Test

Dear Shell API Team,

We have successfully created and configured our application GoPilot in the Shell Developer Portal to integrate with the Shell EV Public Locations API v2.1.2.

Our current setup shows:

Application status: Approved
Credential status: Approved
B2B EV Locations: Enabled
Environment: Test
OAuth2 client credentials authentication is successful
We successfully receive an OAuth access token
However, when using this access token to call the B2B EV Locations endpoint:

GET /ev/v2/locations/nearby

the Shell API returns:

HTTP 401 – Unauthorized

We have also tested the authentication and API call independently of our GoPilot application and receive the same result.

Could you please check whether our application/credentials have the correct entitlement for the B2B EV Locations API in the test environment, or advise if an additional step is required before we can access the API?

Our goal is to use the API in GoPilot to display EV charging locations, charging capabilities and real-time charger availability.

Thank you for your help.

Kind regards,

Roderick Voerman
GoPilot
mygopilot.app

Obtenir Keys Client-id, Client-secret pour tester les Api Shell (POST Transactiondata/V1 par exemple) afin de remplacer l'importation via excel du fleet-hub trop lourde.
Le soucis mon email perso jean-luc.billard@wanadoo.fr n'est pas connu de vos services (c'est l.mariage@lokea.fr qui est utilisé habituellement et je n'y ai pas accès pour récupérer les codes de sécurité) comment procéder pour acceder à My Apps avec mon mail perso? TEPIF est client FR94860575
Merci pour votre retour

Hi,

We registered the app "2Topics Platform" (Consumer Key 84tLH8Nd3mEyJ7YEg2hGVXGzX7Y45oZi) with the B2B Data And Reporting products (Basic/Advanced/Premium, all approved) to integrate the B2B Mobility Card Transaction Data API into our fleet management platform.

OAuth token requests against the test environment work fine, but every call to POST /transaction-data/v1/priced returns Status FAILED with error E0003 "User does not have access to the requested operation" (example RequestId: d5df4c06-92c5-4a54-b6d4-9d0b006ef4bc). The app creation flow also showed: "Account number required to test full functionality. Contact support."

Could you provision a sandbox test account (payer/account number with sample transaction data) for our app so we can validate our integration end to end?

Company: 2Topics (fleet management platform, Netherlands)
Contact: yonnie.kauwenberg@lease-deal.com

Thanks!

V testovacom prostredi poprosim o priradenie k uctu, clietId: NyCYvbqfZz3iRezO50dn0TxgbGDMF3sq zakaznicke cislo: SK00006424. Pristupovy token mi funguje ale dalsie nacitanie konci chybou E0003:
"Status": "FAILED",
"Errors":[ {
"Code": "E0003",
"Title": "Unauthorized",
"Detail": "User does not have access to the requested operation",
"AdditionalInfo": {}

We are MovingTruck, a fleet management / TMS platform used by road transport
companies in Latin America. We would like to request test access to the Fleet
type APIs.

USE CASE
Automatically attribute each Shell Card fuelling to the correct vehicle by its
registration plate (VRN) inside our platform, in near real time, and reconcile
it against priced transactions and invoices for cost-per-trip reporting. Our
primary need is B2B Mobility Card Recent Transaction, supported by Card
Transaction Data, Customer Data, Card Management and Invoice.

WHAT WE HAVE DONE SO FAR
We have created a sandbox app ("MovingTruck - Fuel Card Integration"), which
shows as Approved with 8 API products Enabled. We successfully obtained an
OAuth token from POST /v2/oauth/token (HTTP 200).

However, every Fleet endpoint returns HTTP 403 / E0006 "User does not have
access to the requested operation":

- POST /user-management/v1/loggedinuser 403 E0006
- POST /customer-management/v1/payers 403 E0006
- POST /customer-management/v1/accounts 403 E0006
- POST /card-management/v1/search 403 E0006
- POST /transaction-data/v1/pricedtransaction 403 E0006
- POST /transaction-data/v1/recent 400 E0003 "No data found"

Only POST /config-data/v1/purchasecategory returns data successfully.

Reference RequestId for the 403 on /user-management/v1/loggedinuser:
b401b80b-599a-49b7-b07d-731720ca3f14

This matches the documentation stating that your API Support team needs to
create and customise a Mobility Customer account in your fleet management
system. Could you please set that up for our sandbox app so we can complete
testing?

NOTE ON THE ACCOUNT NUMBER FIELD
We are a third-party software provider acting on behalf of Shell Fleet
Solutions customers who hold their own Shell Card agreements. We do not hold
a Shell customer account of our own.

QUESTIONS

1. MARKET COVERAGE (most important)
Our customers operate in Chile, and some in Brazil. The Regional
Availability page lists only European and Asian markets. Can you confirm
whether Shell Card transactions issued in Chile (Enex S.A.) or Brazil
(Raizen) are reachable through these APIs? If they are not, what is the
supported route to obtain fuel transaction data for those markets?

2. MULTI-TENANCY
Can a single partner app access multiple payers, with each customer's
authorisation, or does each customer require its own set of credentials?
We note that /transaction-data/v1/multipayerspricedtransactions supports
up to 10 payers per request.

3. PRODUCT TIER
Which tier (Basic / Advanced / Premium) of Data & Reporting and Card
Management covers these endpoints?
- POST /transaction-data/v1/recent
- POST /transaction-data/v1/pricedtransaction
- POST /card-management/v1/search
- POST /customer-management/v1/payers

Thank you.

Hello,

Thank you for your previous assistance.

Using the test data you provided:

ColCoCode: 5
PayerNumber: GB00000001

we are now able to successfully authenticate and use the following Invoice API endpoints in the TEST environment:

- POST /invoice-management/v1/dates
- POST /invoice-management/v1/search

Both endpoints return successful responses and invoice data.

For example, the Search API returns invoice records such as:

InvoiceId: 1718
SummaryDocumentId: 1023
PayerId: 2
PayerNumber: GB00000001
ColCoId: 5

However, when attempting to use:

POST /invoice-management/v1/download

we receive the following response:

Code: E0003
Title: Unauthorized
Detail: Supplied credentials are invalid or user does not have access to the operation

We have already supplied the required parameters identified through validation responses, including:

- ColCoId
- ColCoCode
- ColCoCountryCode
- PayerId
- PayerNumber
- InvoiceId or SummaryDocumentId

Could you please provide:

1. A valid example request body for the Download endpoint.
2. Confirmation whether download access is enabled for the TEST payer GB00000001.
3. Confirmation whether InvoiceId 1718 and/or SummaryDocumentId 1023 can be used for download testing.
4. Details of any additional permissions, references or document identifiers required for the Download endpoint.

Thank you for your support.

Kind regards,

János Varju
Managing Director
Fraxinus Kft.

Subject:
B2B Mobility Invoice API - TEST Environment - HTTP 504 on Search and Dates Endpoints

Hello,

We are currently integrating the B2B Mobility Invoice API in our system and testing against the TEST environment.

OAuth authentication is working successfully.

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

Using our Consumer Key and Consumer Secret, we successfully receive a valid Bearer access token.

However, when calling the Invoice API endpoints in the TEST environment, we receive HTTP 504 Gateway Timeout responses.

Affected endpoints:

POST https://api-test.shell.com/test/invoice-management/v1/search

POST https://api-test.shell.com/test/invoice-management/v1/dates

Request parameters used:

ColCoCode: 34
PayerNumber: HU53454749

Example response:

HTTP 504 Gateway Timeout

{
"RequestId": "2b0cbe11-f109-4c43-9201-49af0370df1c",
"Status": "FAILED",
"Errors": []
}

Could you please verify:

1. Whether the TEST application has been provisioned correctly for the B2B Mobility Invoice API.
2. Whether payer HU53454749 is linked to our application.
3. Whether ColCoCode 34 is the correct value for this payer.
4. Whether the Invoice API backend is currently available in the TEST environment.
5. Whether any additional configuration or entitlement is required before using the Search and Dates endpoints.

Thank you for your support.

Kind regards,

János Varju
Managing Director
Fraxinus Kft.

We are currently completing our integration with the Shell EV Public Locations v2 API on the UAT environment ([https://api-test.shell.com](https://api-test.shell.com)). Our codebase has been updated to follow the latest v2.1.2 specifications, and we are performing end-to-end testing from our environment.

During terminal and integration testing, we encountered an authorization issue where OAuth authentication succeeds, but access to the v2 locations endpoint is rejected.

1. Successful Step: OAuth 2.0 Token Generation
We successfully requested an access token via client_credentials grant on the token endpoint:

Endpoint: POST [https://api-test.shell.com/v1/oauth/token](https://api-test.shell.com/v1/oauth/token)

Client ID: A6l4VHUWGJBdvohb1Ziy229GP2D8FYn2

Result: 200 OK — Returns a valid Bearer token (access_token, expires_in: 899).

2. Failed Step: GET Request to /ev/v2/locations
When attempting to call the EV locations endpoint using the freshly generated token and a valid UUID RequestId header:

Endpoint: GET [https://api-test.shell.com/ev/v2/locations?country=NLD&perPage=1](https…)

Headers sent:

Authorization: Bearer <valid_access_token>

RequestId: <UUID>

Response Received:

HTTP Status: 401 Unauthorized

Payload:

JSON
{
"requestId": "3A3E3FE0-C223-4C4E-A3FB-6584C7BAF99E",
"status": "FAILED",
"errors": [{
"code": "E0003",
"message": "Unauthorized",
"description": "unable to authenticate request",
"details": []
}]
}
3. Conclusion & Request
Since the token exchange is successful and the HTTP request structure strictly adheres to the v2 specification, it appears that the EV Public Locations v2 product/scope is not yet provisioned or enabled for our test Client ID (A6l4VHUWGJBdvohb1Ziy229GP2D8FYn2) in the api-test environment.

Could you please verify our API product permissions and enable access to EV Public Locations v2 for this Client ID?

Please let us know once activated or if you require any additional logs or cURL requests from our end.

Case 10689204 ("Request access to Fleet Transaction Data") was marked Resolved on 28 July 2026, but no reply or solution summary was posted on the ticket page, and we still cannot access the API.

App: Atipat Fleet Fuel Data Integration (Key Status: Approved)
Environment: Test (https://api-test.shell.com/test)
Fleet accounts: TH00013977 (ATHIPAT TOUR LTD PART) and TH00013978 (NEW ATIPAT CO LTD)

Current result (retested 28 July 2026):
1. Token request to https://api-test.shell.com/v2/oauth/token with grant_type=client_credentials returns HTTP 200 and a valid access token.
2. POST /transaction-data/v1/priced with header RequestId and body
{"Filters":{"ColCoCode":"...","InvoiceStatus":"A","IncludeFees":true,"PayerNumber":"TH00013977","FromDate":"2026-04-29 00:00:00","ToDate":"2026-07-28 00:00:00"},"Page":1,"PageSize":50}
returns HTTP 401:
{"RequestId":"d739edfc-104b-42c2-8b1a-d40c793fa709","Status":"FAILED","Errors":[{"Code":"E0003","Title":"Unauthorized","Detail":"User does not have access to the requested operation","AdditionalInfo":{}}]}
3. The same 401 is returned for TH00013978, and for every ColCoCode value we tried (empty, "5", "86"), so this does not appear to be a payload validation issue - an invalid payload returns 400 / E0001 instead.

Could you please:
1. Confirm whether fleet account TH00013977 has actually been entitled to the B2B Mobility Card Transaction Data API product for this app, and enable it if it has not.
2. Provide the correct ColCoCode (company code) for our accounts. This is a mandatory request field and we have never been given the value.
3. Advise on case 10689173 (linking the second fleet account TH00013978 to the same app), which is still In progress.

Moin Support,

vielen Dank für die Aktivierung des Testzugangs. Wir haben die Anbindung im Testsystem erfolgreich umgesetzt und möchten nun in Production gehen.


Was bereits funktioniert (Test):
* Die App „logi_flows" ist freigegeben; als „Enabled" angezeigt werden B2B Data and Reporting Advanced, B2B Invoice Advanced und B2B CardManagement Advanced.
* Der OAuth-Token-Abruf funktioniert (HTTP 200).
* Aufrufe an POST /transaction-data/v1/priced liefern HTTP 200, Status SUCCESS – die technische Anbindung steht.
* Im Testkonto liegen allerdings keine Daten (TotalRecords: 0 für alle Payer GB00000001, GB00000097, CZ00002080 und alle InvoiceStatus). Für einen realistischen Betrieb möchten wir daher direkt auf Production wechseln.


Zwei offene Punkte, bei denen wir Ihre Hilfe brauchen:
1. Production-Freischaltung für unseren Endkunden BeFresh Logistic GmbH & Co. KG. Wir möchten live abrufen:
* B2B Data and Reporting – die Tankvorgänge (Liter, Preis, Fahrzeug, Fahrer) für die operative Kostenauswertung.
* B2B Invoice – die Rechnungen (Netto/Brutto, MwSt., Abrechnungszeitraum) für den buchhalterischen Controlling-Bericht und den Abgleich mit den Transaktionen.
2. Berechtigung für die Invoice-Operation. Bei Tests gegen POST /invoices/v1/list erhalten wir mit unserem Consumer Key die Antwort E0003 – user does not have access to the operation, obwohl „B2B Invoice Advanced" für die App als „Enabled" angezeigt wird. Bitte ordnen Sie die Invoice-Operation unserem Consumer Key zu (Test und Production).


Bitte teilen Sie uns dafür mit:
1. Die Production-Zugangsdaten (Client ID / Client Secret) bzw. wie wir die App für Production freischalten.
2. Die Production-Basis-URL (vermutlich https://api.shell.com) und die korrekten Endpunkt-Pfade für Transaktionen und Rechnungen.
3. Die korrekten ColCo- und Payer-Nummern für das Shell-Fleet-Konto von BeFresh Logistic
4. Falls für Production ein zusätzlicher Freigabe-/Onboarding-Schritt nötig ist: was benötigen Sie von uns?


Über eine kurze Rückmeldung freuen wir uns.
Viele Grüße