Tap Payments Cards API
Saved cards (card-on-file) attached to a customer.
Tap Payments Cards API is one of 10 APIs that Tap Payments publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Cards. 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 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.
Requests are made against a single base URL, https://api.tap.company/v2.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Tap Payments Cards API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
bearerAuth— Secret API key passed as a Bearer token in the Authorization header: Authorization: Bearer sktest... (test) or sklive... (live). Keys are issued from the Tap d…
Paths & Operations 3
Across 2 paths, the API surfaces 3 operations — 1 DELETE, 2 GET. Each is listed below with its method, path, parameters, and response codes.
Saved cards (card-on-file) attached to a customer.
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Card (7 properties), DeleteResponse (3 properties), Error (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 Tap Payments 9
Other APIs Tap Payments publishes across the network.