Resolve Orders API
An order represents an authorization of credit for a customer transaction. Once authorized, an order can be partially or fully captured as goods or services are fulfilled, or canceled if the transaction does not proceed.
Resolve Orders API is one of 12 APIs that Resolve publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Orders. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 6 operations across 4 paths, and defines 14 schemas. It is described by OpenAPI 3.0.0, at version V5.
Requests are made against a single base URL, https://app-sandbox.resolvepay.com/api.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Resolve Orders API declares
2 security schemes
for authenticating requests.
It accepts HTTP basic authentication (basicAuth).
It accepts HTTP bearer tokens (JWT) (bearerAuth).
By default, every request must be authenticated.
basicAuth— HTTP Basic Auth using merchantid as username and the merchant secret key as password.bearerAuth— Bearer token authentication using an OAuth access token minted for an API access key created in Merchant Dashboard.
Paths & Operations 6
Across 4 paths, the API surfaces 6 operations — 2 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
An order represents an authorization of credit for a customer transaction. Once authorized, an order can be partially or fully captured as goods or services are fulfilled, or canc…
Schemas 14
The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Order (19 properties), OrderListItem (18 properties), OrderCreateRequest (8 properties), OrderLineItem (7 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 Resolve 11
Other APIs Resolve publishes across the network.