Test

Hello Shell Developer Support,

I am requesting access to the Shell Loyalty Transactions API for Louro, a vehicle ownership and maintenance platform operated by Opaius Inc.

This request is for a U.S. consumer loyalty integration and is not related to Shell B2B Mobility Cards or fleet-card management.

Louro would allow customers to voluntarily connect their Shell loyalty accounts through Shell Single Sign-On. With customer authorization, Louro would retrieve qualifying Shell transaction history to provide:

- Automated fuel and charging history
- Fuel spending and vehicle operating-cost tracking
- Fuel-economy insights
- Vehicle ownership and maintenance insights
- Verified in-app achievements based on legitimate vehicle activity

We reviewed Shell’s Quick Start Guide for Retrieving Transactions of a Customer and understand that Shell must provide and configure:

- Shell SSO Client ID
- API Management Gateway Client ID
- API Management Gateway Client Secret
- Approved OAuth scopes
- Whitelisted redirect URLs
- Test or sandbox access

Could you please advise on the onboarding process for U.S. access to the Loyalty Transactions API?

We would also appreciate clarification on:

1. Whether Shell Fuel Rewards accounts in the United States are supported
2. How to obtain test credentials and a test customer account
3. Which read-only OAuth scopes are required
4. Whether a Shell fleet account is required for this consumer Loyalty API
5. The security, commercial, and production approval requirements
6. How redirect URLs should be submitted for development, staging, and production
7. Transaction synchronization latency and applicable rate limits
8. Whether webhooks are available for new transactions

Company: Opaius Inc.
Product: Louro
Website: https://opaius.com
App: https://louro.opaius.com

Thank you,

Kaya Wesley
Founder & CEO
Opaius Inc.

Double AA Corporation is an existing Shell MarketHub US Commercial Fuels wholesaler. Please enable the Document API for US Fuels for Angelina, our internal 24/7 dispatch integration, in both test and production.

The API is visible in the catalog, but it is not available in My Apps > Add app, and this developer account currently has no apps. Please grant this developer account access, map Sold-To 12666269 and Payer 12665373, and provide the API product subscription plus client_id, client_secret, and apiKey.

Required documents: rackPrice, contractPrice, invoices including credit/rebill documents, DSA, DFT, and SOA. Shell's MarketHub 2.0 Integration Guide also documents allocations, BOLs, combined settlement, chargeback/RFCO, unsettled transactions, and monthly transactions. Please confirm and enable all documents available to this wholesaler.

Please also confirm whether GPO/allocation increase requests have an authorized API. If not, identify the approved TABS or human workflow. Angelina will be read-only unless Shell explicitly authorizes an allocation-request operation.

Please provide sandbox/sample payloads, rate limits, required terms or addendum, production approval steps, and a technical onboarding contact. Related MarketHub service request: 24633917.

Hi Shell Team,
I hope you're well.
We are currently building ARRAiVO, an innovative platform designed to enhance mobility and transportation experiences through intelligent technology and seamless integrations.
As part of our development roadmap, we would like to explore the possibility of integrating ARRAiVO with Shell's EV charging infrastructure. We believe there could be significant mutual value in enabling our users to access and utilise Shell EV charging stations through our platform.
We would welcome the opportunity to discuss your integration capabilities, available APIs, partnership requirements, and any technical considerations with your team.
Would it be possible to arrange a 20-minute call with your technical team at a time convenient for you?
We look forward to learning more about how we might work together.
Kind regards,
Alban Tobli
ARRAiVO

Toll management is becoming an increasingly important topic within our organization with the introduction of truck tolling in the Netherlands. We have developed several reports based on data from Shell FleetHub. However, we would like to automate these reports by retrieving the data directly from the Shell APIs.

Until recently, it did not appear that a dedicated API was available. However, I found several reference pages mentioning the availability of endpoints that provide relevant data. These pages include:
https://developer.shell.com/api-catalog/b2b-mobility-toll-vehicle-manag…
https://developer.shell.com/api-catalog/b2b-mobility-toll-order-and-boa…
https://developer.shell.com/api-catalog/b2b-mobility-toll-master-data/q…

Additionally, I noticed that Shell has updated its API documentation and now provides the following pages:
https://developer.shell.com/api-catalog/v1.0.0/b2b-mobility-toll-vehicl…
https://developer.shell.com/api-catalog/v1.0.0/b2b-mobility-toll-master…

We kindly request access to these APIs to test their functionality and retrieve data so that we can ingest it into our data warehouse.

Sincerely,
Niels Hakkers

Can you please assist me in getting started on the early stages of building the shell API
need to know what the callback url is
any other information required for testing and token pulling

Dear

We are doing our swith to oAuth. Part of this process involves the migration to customer-management/v1/pricelist. However, we get an unauthorized error. We used our test account GB00000043.
Error:
{
"RequestId": "cfe16d53-cf9c-4fcf-ab73-27eb806c3784",
"Status": "FAILED",
"Errors": [
{
"Code": "E0003",
"Title": "Unauthorized",
"Detail": "Supplied credentials are invalid or user does not have access to the operation",
"AdditionalInfo": {}
}
]
}

Dear

We are switching to oAuth and would like to use the card-restrictions/v1/update. When we do a call we get error:
{
"fault": {
"faultstring": "Unable to identify proxy for host: https_vhost and url: /test/fleetmanagement/card-restrictions/v1/update",
"detail": {
"errorcode": "messaging.adaptors.http.flow.ApplicationNotFound"
}
}
}
We suspect that the endpoint 'fleetmanagement/card-restrictions' was wrong in the documentation so we also tried '/test/card-restrictions/v1/update' resulting in:
"Code": "E0003",
"Title": "Unauthorized",
"Detail": "Supplied credentials are invalid or user does not have access to the operation",
"AdditionalInfo": {}

PowerBI API Request

Hello, I'm looking to get an app set up using Shell's APIs specifically the ones relevant to card transactions and invoices, which I believe are these ones:

B2B Data And Reporting Premium
B2B Invoice Advanced
B2B Invoice Basic
B2B Data And Reporting Basic

I'm requesting access so I can use these APIs in a test environment. Thank you!

Case ID: 10451403 - Marked as Resolved, but I can't see any reply!