bp Open Fleet Aral AppConnect (Pay@Pump) API
Digital fuel authorization at bp and Aral stations. Drivers authorize a fuel card directly from the vehicle, avoiding the till; the card is linked to a driver, vehicle or onboard computer and only the appropriate nozzle is released. Eight operations cover site search by coordinate and radius, site detail, payment-method registration and removal, and starting, checking and cancelling a fuelling session. Authorizations are tokenized and validated against existing fuel card controls including velocity limits and site restrictions. The only write surface on the platform, and it has no idempotency mechanism. Germany only. Published rate limit 100 requests per second.
bp Open Fleet Aral AppConnect (Pay@Pump) API is one of 7 APIs that BP publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Energy, Retail Fuel, Payments, Mobility, and Fleet. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.
This API exposes 8 operations across 6 paths, organized into 4 resource areas, and defines 28 schemas. It is described by OpenAPI 3.0.1, at version 1.
Requests are made against the base URL https://api.fleet.bp.com/{apiPrefix}/v1/.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
bp Open Fleet Aral AppConnect (Pay@Pump) API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as Authorization (Bearer).
By default, every request must be authenticated.
Bearer— JWT Authorization header using the Bearer scheme (Example: 'Bearer 12345abcdef')
Paths & Operations 8
Across 6 paths, the API surfaces 8 operations — 1 DELETE, 4 GET, 2 POST, 1 PUT. They span 4 resource areas: Fueling, HealthCheck, PaymentMethod, SiteDiscovery. Each is listed below with its method, path, parameters, and response codes.
Schemas 28
The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are pol_service_api.Models.Events.Receipt (12 properties), pol_service_api.Models.Dsp.Address (7 properties), pol_service_api.Request.Txo.InitiateFuelingRequest (7 properties), pol_service_api.Models.Dsp.RetailSite (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from BP 6
Other APIs BP publishes across the network.
This is an independent, third-party profile of bp Open Fleet Aral AppConnect (Pay@Pump) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.