How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

bp Open Fleet Transaction Management API

Direct access to fleet fuel transaction data. GET /transactions returns full transaction detail including product breakdowns, site location, driver and vehicle information, discounts, taxes and invoicing status, searchable by vehicle registration, cardholder, invoice number, country and date. The widest entity on the platform at 77 response properties. Available in AT, BE, DE, LU, NL, PL, PT, ES and UK. Published rate limit 10 requests per minute.

bp Open Fleet Transaction Management 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, Fleet, Transactions, Fuel Cards, and Developer Platform. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.0.1, at version v1.0.

Requests are made against the base URL https://api.fleet.bp.com/{apiPrefix}/v1.0/.

1 operations 1 paths 4 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v1.0
Base URL
https://api.fleet.bp.com/{apiPrefix}/v1.0/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

bp Open Fleet Transaction Management 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 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

OpenApiTransactions 1
GET
/transactions
7 params → 200400500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are OpenApiTransactionResponse (77 properties), ResultEntity (4 properties), OpenApiTransactionsResponse (3 properties), ErrorDetailsEntity (2 properties). Each schema is shown below with its type and property counts.

ResultEntity
object
4 properties
ErrorDetailsEntity
object
2 properties
OpenApiTransactionResponse
object
77 properties
OpenApiTransactionsResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bp-fleet-transaction-management-openapi.json Raw ↑

Other APIs BP publishes across the network.

BP API Marketplace
bp Open Fleet Authentication API
bp Open Fleet Card Management API
bp Open Fleet Invoice Management API
bp Open Fleet Retail Site Information API
bp Open Fleet Aral AppConnect (Pay@Pump) API
Where this information came from

This is an independent, third-party profile of bp Open Fleet Transaction Management 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.