Authorization Error
We are trying to test the "https://api-test.shell.com/ev/v2/locations" API but end up receiving 401 response code. We tried passing the Access token obtained from both `/v1/oauth/token` and `/v2/oauth/token` authorization endpoints.
Need some help in setting up these APIs.
Api Keys
hi
i just set up an app with in your plat form im trying to get my client id and secret to test my implementation. I see a info tool tip beside the app saying i may need a fleet account number i do not have one and do not see any documentation of where or how to get one. im looking to use the EV locations and mobility-EV api's to allow my user to find and manage charging sessions with your platform form within my platform. if you could please let me know what is needed in order for me to get my client id and secret that would be much appreciated.
Many Thanks,
Evan
Going Live
Please enable production access for our Shell Developer credentials for the B2B Mobility Card Transaction Data API.
We have completed sandbox testing for the Priced Transaction Data endpoint and are ready to move to production for fleet account PH07782421.
Endpoint requested:
POST /transaction-data/v1/priced
Business use:
We will use Shell Fleet transaction data in FleetGuard Pro, our internal fleet operations system, to augment vehicle usage and refueling records. The integration imports refueling transaction details such as transaction date/time, vehicle registration, site name, receipt number, quantity, unit price, gross amount, VAT/tax-related fields, and invoice-related fields. These records are matched to vehicles in FleetGuard Pro for fuel usage tracking, cost visibility, reconciliation, reporting, and fleet analytics.
Sandbox validation completed:
- OAuth client credentials authentication tested successfully.
- Priced Transaction Data endpoint tested successfully.
- Fuel-only transaction fetch tested using IncludeFees = false and FuelOnly = true.
- Pagination, transaction line handling, and idempotent loading have been implemented.
- Data is stored securely in SQL Server and accessed only by authorized FleetGuard Pro users.
Please map/enable our production credentials for fleet account PH07782421 and advise if there are any production-specific request body values we should use, especially ColCoCode, PayerNumber, and any account mapping details.
ColCoCode and PayerNumber for Test
Hello,
Can you please provide me ColCoCode and PayerNumber for TEST stage, so I can test my implementation ?
Best regards,
Request for integration
Hello,
I would like to ask for b2b invoice api integration for the accounts of these companies under the same corporate umbrella:
Schubert partner a.s. no. CZ00003118
JEŘÁBEK & VODRÁŽKA no. CZ56893979
AGRO PRODUKCE s.r.o. no. CZ56892852
VEJCE CZ s.r.o. no. CZ00007040
Thank you
Filip Matěja
API Access/Account Linking
Hi,
I have been tasked with integrating our Shell gas card purchase information into our custom CRM. The instructions say I need to request access. Please link my developer account to my company's account:
Account Name: TRASH IT JUNK REMOVAL LTD
Account Number: 0460002211357
Parent: Shell Fleet Plus Canada (Primary)
If you need more information, please feel free to reach out.
Best regards,
Ming Tan
ming@allaccess.ca
Can not acces data
I am trying to retreive data from https://api-test.shell.com/transaction-data/v1/recent. I am able to get a token but the request fails. Can you send me a working request?
Sandbox Access Enablement Request
Sandbox Access Enablement Request - FleetGuard Pro - Mobility Transaction and Customer Data APIs
Hello Shell API Support,
We request sandbox access enablement for our approved app.
App Name: FleetGuard Pro
Environment: api-test.shell.com (sandbox)
Client ID: aVijojkAlaNYpl1jf9ZChLTT8XO9pHH1
Required API access:
B2B Mobility Card Transaction Data
POST /transaction-data/v1/pricedtransaction
B2B Mobility Customer Data
POST /user-management/v1/loggedinuser
POST /customer-management/v1/payers
Use case:
We are integrating Shell Fleet card refuel-event retrieval for testing and schema validation.
Current behavior:
OAuth token generation succeeds, but the endpoints above return E0006 Forbidden ("User does not have access to the requested operation").
Sample RequestIds:
cb968db0-f8ef-4952-a07f-6078cceb5ecd (loggedinuser)
6bdaf08c-1a9b-434c-88a9-23628739eabb (loggedinuser with ColCoId)
6624fc3c-872f-47eb-97fe-4b9d53ed6215 (payers)
d9b9eab4-754a-43f9-b814-ae82e181bc7f (payers alt payload)
00fa988a-f7f4-41b9-8335-06af151e62eb (pricedtransaction with payer)
Test context:
ColCoId: 1
PayerNumber: PH07782421
Please enable the required sandbox entitlements/subscriptions for this client and confirm once active so we can re-test.
Thank you.
Activate sandbox access (Stratoss app)
Hi,
I've registered a sandbox application "Stratoss" on developer.shell.com
(client_id: 1kXpDAbqsyRf3OttiwvyHate9h5UPgFf).
OAuth works, but every call to /transaction-data/v1/* returns
403 E0006 "User does not have access".
Please activate sandbox access for my client_id and provide test
credentials (AccountNumber, PayerNumber, ColCoId, ColCoCode,
ColCoCountryCode).
Pagination
- Previous page ‹‹
- Page 4
- Next page ››
