Mobility · API V1

Fuel card

Export odometers and reports from a Shell fleet account.

Controlled, account-enabled access

WHAT IT SOLVES

Bring Fuel card into your workflow

Export odometers and reports from a Shell fleet account. This public page presents the use case and a safe preview; operational configuration is managed inside the portal.

  • Automate checks connected to vehicles and mobility.
  • Bring the result into onboarding, renewals, reconciliation, and internal controls.

REQUEST DATA

What the Fuel card API uses

The public page for this version uses Integration and Flow.

integracionIntegration
Text valueRequired
flujoFlow
Text valueRequired

API V1Up to 1 item per requestJSON

INTEGRATION FLOW

From a request to structured output

  1. 01Define the request

    Start with your use case and the minimum required data.

  2. 02Enable access

    We configure scope, credentials, and capacity for your account.

  3. 03Integrate the result

    Consume JSON inside your product or operating workflow.

MANAGED CONFIGURATION

This integration is configured in the portal

It requires account-managed secret references. The public site never displays or requests those credentials.

FREQUENTLY ASKED QUESTIONS

Questions about Fuel card

What can the Fuel card API be used for?

Export odometers and reports from a Shell fleet account.

What input does the Fuel card API accept?

The public v1 contract accepts integracion and flujo. This page identifies which fields are required or optional.

How many items can one request include?

Up to 1 item per request.

Can I try the Fuel card API on this page?

This integration requires account-managed configuration. The public site never requests or displays secret references.

How is access enabled?

Access is controlled and enabled per account. Requests and operational configuration are managed through the API.ar portal.

NEXT STEP

Take Fuel card to production

Open the portal to request access and continue with a secure integration.

Open the portal