Chariot inboundTransfers API
The inboundTransfers API from Chariot — 5 operation(s) for inboundtransfers.
Chariot inboundTransfers API is one of 29 APIs that Chariot publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include inboundTransfers. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 6 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.0.0, at version 6.0.
Requests are made against 2 base URLs: https://api.givechariot.com/fdx/v6, https://devapi.givechariot.com/fdx/v6.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Chariot inboundTransfers API declares
1 security scheme
for authenticating requests.
It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 2 scopes.
By default, every request must be authenticated.
oauth2— OAuth 2.0 Bearer token. A client may hold both scopes, but each FDX authorization must contain exactly one — they are mutually exclusive per authorization. An…
Paths & Operations 6
Across 5 paths, the API surfaces 6 operations — 2 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are InboundTransfer (6 properties), ProblemDetails (4 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 Chariot 12
Other APIs Chariot publishes across the network.