Resolve Access Keys API
OAuth access keys are created in Merchant Dashboard and can be exchanged for bearer tokens.Use the `/access-keys/token` endpoint to mint a bearer token from a valid `client_id` and `client_secret`.
Resolve Access Keys API is one of 12 APIs that Resolve publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Access Keys. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 1 operation across 1 path, and defines 8 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 Access Keys 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 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
OAuth access keys are created in Merchant Dashboard and can be exchanged for bearer tokens. Use the /access-keys/token endpoint to mint a bearer token from a valid clientid and cl…
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are AccessKeyTokenResponse (4 properties), IssueAccessKeyTokenRequest (2 properties), ValidationError (1 property), ForbiddenError (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 Resolve 11
Other APIs Resolve publishes across the network.