Test

Hi team,
My name is Aabi from Manage Vehicle Software. We are developing a fleet management platform and would like to explore integrating with Shell to give our users visibility of their vehicle fuel spend.
I have obtained the Client ID and Client Secret for our platform
Specifically, we are looking to:
- Access fuel transaction data via the Shell on behalf of our users
What is the next process of logging in the users and getting their transaction information?

Dear API Team,

My name is Boyd, and I am a co-founder of T.A. Tech Inc. We are a payment marketplace specializing in facilitating e-wallet transactions between consumers and businesses.

We are reaching out to explore enabling e-wallet payments at Shell gas pump terminals. We currently have an application for peer-to-peer tipping and are expanding our services to include point-of-sale payment options. Our technology allows customers to use popular e-wallets like PayPal, Venmo, Cash App, Google Pay, Apple Pay, and Samsung Pay to purchase gas. We believe this would provide a valuable customer experience, as e-wallets are projected to become the primary payment method for both in-store and online transactions by 2033.

We are reviewing your API but have some questions about its implementation.

Once we integrate the shell API, will our ewallet solution be immediately available in all Shell gas stations?

How would customers visiting the locations know that they can now use their PayPal wallet or Cash App to pay for fuel?

Do we need to contact the franchisee for that location or those locations to activate the new payment option etc?

Boyd
Chief Strategy Officer
T.A. Tech Inc

Hello!

I'm the owner of https://olcsontoltok.hu. It is an EV charger aggregator site for Hungary. I would like to get access to your EV Location API so that I can accurately represent your EV chargers on my site. The site currently has around 2000 EV chargers listed (including yours).

Thanks, Adam

Dear Sir/Madam,

I am currently developing an application intended for transport and logistics companies in Croatia, and I am exploring the possibility of integrating fuel card data—specifically SHELL fuel cards—into my system via your APIs.

The goal of the application is to provide fleet operators with detailed insights into fuel usage and costs. For example, within the app, a vehicle (e.g., license plate ZG1234HR) would be linked to a specific fuel card (e.g., card number 123456789). I would like to retrieve relevant transaction data such as:

* Fuel purchases made using the card
* Quantity of fuel purchased
* Price per transaction
* Date and location of each transaction

Thank you in advance for your time and assistance. I look forward to your response.

Best regards,
Denis Truhlaž

We are developing a B2B platform for lubricants procurement in Seattle. We have the OpenAPI specs for 'Lubricants Order Management', but these products are not visible in our App settings. We need to verify our relationship or get sandbox access to start integration.

Sayın Shell Filo Çözümleri Teknik Destek Ekibi,

Firmamız TDI Mühendislik Makine San. Ve Tic. Ltd. Şti. olarak Shell Fleet Solutions API entegrasyonu gerçekleştirmekteyiz.
Kullandığımız ERP sistemimize yakıt işlem verilerini otomatik olarak çekmek istiyoruz.
Ancak API çağrılarımızda yetkilendirme hatası almaktayız.

Firma / Hesap Bilgileri:
• Müşteri Kodu (Payer Number): 0013022989
• Müşteri Adı: TDI Mühendislik Makine San. Ve Tic. Ltd. Şti.

• API Uygulama Bilgileri (Developer Portal):
• Consumer Key: RCbJOsEe5p8eOjkoXrn9aAqkYsSyR3Kt
• Key Status: Approved
• Oluşturulma: Developer Portal üzerinden
• Abone olunan API'ler:
• B2B CardManagement Basic — Enabled
• B2B EV Locations — Enabled
• B2B Invoice Basic — Enabled
• B2B Data And Reporting Basic — Enabled
• B2B Digital Payment Basic — Enabled
Sorun:
OAuth 2.0 token başarıyla alınmaktadır (POST /v2/oauth/token — 200 OK). Ancak transaction data endpoint'lerine istek gönderdiğimizde yetkilendirme hatası alıyoruz:

Deneme 1:
• Endpoint: POST https://api-test.shell.com/transaction-data/v1/priced
• PayerNumber: TR13022989
• Yanıt: 401 — E0003 Unauthorized — "User does not have access to the requested operation"

Deneme 2:
• Endpoint: POST https://api-test.shell.com/transaction-data/v1/pricedtransaction
• PayerNumber: TR13022989
• Yanıt: 403 — E0006 Forbidden — "User does not have access to the requested operation"

Deneme 3:
• Endpoint: POST https://api-test.shell.com/transaction-data/v1/pricedtransaction
• PayerNumber: 0013022989
• Yanıt: 403 — E0006 Forbidden — "User does not have access to the requested operation"

Örnek Request Body:
{
"Filters": {
"ColCoCode": "038",
"ColCoId": 38,
"PayerNumber": "TR13022989",
"FromDate": "2026-03-01 00:00:00",
"ToDate": "2026-03-31 23:59:59",
"InvoiceStatus": "A",
"SortOrder": "1"
},
"Page": 1,
"PageSize": 500
}

Talebimiz:
1. API uygulamamız (Consumer Key: RCbJOsEe5p8eOjko...) ile Payer hesabımız (0013022989) arasında Transaction Data API erişim yetkisinin tanımlanması
2. Türkiye (ColCo 38) için doğru PayerNumber formatının ne olduğunun bildirilmesi (TR13022989 mi, 0013022989 mi, başka bir format mı?)

Konu hakkında yardımlarınızı rica ederiz.

Thank you for responding to my queries, but they are not answering my question or solving my problem. Is there a phone number I can call to resolve these issues with someone who can actually determine what the problem is?

We request that authorization be granted between our API application (Consumer Key: RCbJ...) and our Payer account (0013022989). Access to the B2B Data And Reporting – pricedtransaction endpoint is required. However, we are encountering the following error: E0006 Forbidden.

Hello Shell API Team,

I hope you are doing well.

We are currently building an application that helps users navigate to nearby EV charging stations. As part of this, we would like to integrate Shell’s public EV station APIs.

To proceed with development and testing, we kindly request access credentials (Client ID and Client Secret) for the API.

Could you please guide us on the process to obtain these credentials and any prerequisites required?

Looking forward to your support.

Following from your response to my previous ticket, I have filled out the form for access to your Open Data. I believe that my initial query relates to the access to the EV Public Locations API that probably provides the access to that Open Data under the Public Charge Point Regulations 2023 guidance.

In your developer welcome page, you mention that after requesting access to the developer portal and creating my shell developer account that:

Location APIs (EV Public Locations or Gas station Locations) will be accessible right away.

So, since access to the EV Public Locations API should be open and unrestricted and accessible right away (and I don't seem to have problems authenticating when accessing it) - what is the problem that is causing the failure of the call to the servers?

Thanks

Scott