Skip to main content

Test

Sandbox Creds for EV Charge Sessions API

09345984

Request: Sandbox Credentials for EV Public Charge Sessions API (v1.0.3) - Development Testing

Issue: On the API Catalog page for EV Public Charge Sessions, there is no "Request Access" or "Subscribe" button, preventing self-service onboarding. Per documentation, I'm raising this ticket for manual credential provisioning.

Use Case: Building a Spring Boot EV charging adapter to integrate with Shell Recharge. This prototype routes remote start/stop commands, retrieves session status, and handles webhooks. Testing with virtual data only (e.g., EV Charge Number: NL-TNM-216599-X, EVSE ID: NL*TNM*EVIRTUALCP0002*0).

Steps to Reproduce/Resolve:
1. Generate sandbox/UAT credentials for the test environment.
2. Email them to my developer account [Your Developer Portal Email].
3. Include any setup instructions or test data.

Specific Needs:
- OAuth Credentials: Client ID and Client Secret for token endpoint (https://api-test.shell.com/v2/oauth/token, grant_type=client_credentials).
- API Client Credentials: Additional Client ID and Client Secret for headers (e.g., client_id/client_secret) in charging endpoints<a href="https://api01-uat.shell.com/mobility-ev-api/v1/api/charge-sessions/...&…; target="_blank" rel="noopener noreferrer nofollow"></a>.
- No production or fleet billing required—just sandbox for integration validation.

My Details:
- Developer Account: [nayanthakare2017@gmail.com]
- Company: [Independent Developer]
- Contact: [9307983012]

This will enable quick testing via Swagger/cURL/SDK. Happy to provide more project details or sign an NDA.

Thank you for your support!
[Nayan V Thakare]

Test
Request topic
Other
EV Public Charge Sessions
Endpoint
/charge-sessions/start, /charge-sessions/stop, /charge-sessions/retrieve
Resolved

User does not have access to the request

09314833

Code retour de l'authentification : 200
Jeton : Bearer i5zoHpyVZjDMyFRMI4uCdSgwB3cT

uuid généré : 638d45a8-9b31-4bf0-9b64-67101272cbbe

headers :
{'Authorization': 'Bearer i5zoHpyVZjDMyFRMI4uCdSgwB3cT', 'RequestId': '638d45a8-9b31-4bf0-9b64-67101272cbbe', 'Accept': 'application/json', 'Content-Type': 'application/json'}

body :
{'Filters': {'IncludePayerGroup': 'false', 'IncludeEIDDetails': 'false'}}

Code retour pricedtransactionssummary : 403
Corps de la réponse :
{"RequestId":"638d45a8-9b31-4bf0-9b64-67101272cbbe","Status":"FAILED","Errors":[{"Code":"E0006","Title":"Forbidden","Detail":"User does not have access to the requested operation","AdditionalInfo":{}}]}

A titre d'information, code source python de test :
base_url = "https://api-test.shell.com&quot;
auth_url = "/v2/oauth/token"
accounts_url = "/user-management/v1/loggedinuser"

####################################################################
############ Récupération du Token #################################
####################################################################

# https://api-test.shell.com/v2/oauth/token

response = requests.post(
base_url + auth_url,
auth=HTTPBasicAuth(username, password),
data={"grant_type": "client_credentials" },
verify=False
)

print("")
token = f"Bearer {response.json()["access_token"]}"
print(f"Code retour de l'authentification : {response.status_code}")
print(f"Jeton : {token}")
print("")

####################################################################
############ accounts ################ #############################
####################################################################
# https://api-test.shell.com/user-management/v1/loggedinuser

uuid = str(uuid.uuid4())
print(f"uuid généré : {uuid}")
print("")

headers = {
"Authorization": token,
"RequestId": uuid,
"Accept": "application/json",
"Content-Type": "application/json"
}

body = {
"Filters": {
"IncludePayerGroup": "false",
"IncludeEIDDetails": "false",
}
}

print("headers : ")
print(headers)
print("")
print("body : ")
print(body)
print("")

response = requests.post(
base_url + accounts_url,
headers=headers,
json=body,
verify=False
)

print(f"Code retour pricedtransactionssummary : {response.status_code}")
print("Corps de la réponse :")
print(response.text)

Test
Request topic
RFI
Request ID
638d45a8-9b31-4bf0-9b64-67101272cbbe
B2B Mobility Customer Data
Endpoint
/user-management/v1/loggedinuser
Resolved

User does not have access error

09064663

Hello,

i try to implement a connection to the b2b api. I can retrieve a oauth token like it is described in the documentation. But all endpoints are then giving me this endpoint afterwards.

Sample Response:
https://api-test.shell.com/test/transaction-data/v1/fuelconsumption

Headers (3)
> RequestId:0ef3f2bd-3c8f-4fa8-86ad-c7fe394e1e1e
> Authorization:Bearer anO4xB9U86IuzADKp6OkPKW8TBwu
> content-type:application/json

Response:
{
"RequestId": "0ef3f2bd-3c8f-4fa8-86ad-c7fe394e1e1e",
"Status": "FAILED",
"Errors": [
{
"Code": "E0006",
"Title": "Forbidden",
"Detail": "User does not have access to the requested operation",
"AdditionalInfo": {}
}
]
}

What do I have to configure to get the API working?

Greetings
Tobias

Test
Request topic
Implementation Support
Request ID
0ef3f2bd-3c8f-4fa8-86ad-c7fe394e1e1e
B2B Mobility Card Management
Endpoint
/transaction-data/v1/fuelconsumption
Resolved

Sandbox environment outage (Resolved)

Service
Environment
Environment
STATUS MESSAGE
Status
Outage
Title
Sandbox environment outage
Description

Dear customer,

The sandbox environment is currently experiencing an unexpected outage. Our team is actively working to resolve the issue and restore services as soon as possible. We apologize for any inconvenience this may cause and appreciate your patience.

Next Update:
Fix is expected to be delivered on February 12, 2025.

Contact:
For questions or further support, please contact us at api@shell.com.

POSTED:

Sandbox Environment Downtime (Resolved)

Service
Environment
Environment
STATUS MESSAGE
Status
Outage
Title
Sandbox Environment Unavailability Notice
Description

 

Dear customer,

The sandbox environment is currently experiencing an unexpected outage. Our team is actively working to resolve the issue and restore services as soon as possible. We apologize for any inconvenience this may cause and appreciate your patience.

Next Update:
We will provide an update on February 11, 2025, or sooner if the environment becomes available earlier.

Contact:
For questions or further support, please contact us at api@shell.com.

POSTED:
Subscribe to Test

About us

The Shell Developer Portal supports partners in onboarding to Shell APIs and turning ideas into production-ready solutions.

 

Shell logo

Contact

Login to your account

Ask AI Assistant about Shell APIs and API Products