Duffel Payments API
Pay for held orders.
Duffel Payments API is one of 10 APIs that Duffel publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 3 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version v2.
Requests are made against a single base URL, https://api.duffel.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Duffel Payments API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
bearerAuth— Authenticate with your Duffel access token as a Bearer token in the Authorization header (Authorization: Bearer YOURACCESSTOKEN).
Paths & Operations 3
Across 2 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Pay for held orders.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Payment (3 properties), CreatePayment (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Duffel 9
Other APIs Duffel publishes across the network.
This is an independent, third-party profile of Duffel Payments 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.