Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tap Payments Customers API

Customer records for vaulting and recurring payments.

Tap Payments Customers 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 Customers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 2 paths, and defines 4 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.

5 operations 2 paths 4 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.tap.company/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Tap Payments Customers 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 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Customers 5

Customer records for vaulting and recurring payments.

POST
/customers
Create a customer
createCustomer body → 200401
GET
/customers
List all customers
listCustomers → 200401
GET
/customers/{customer_id}
Retrieve a customer
retrieveCustomer 1 param → 200401404
PUT
/customers/{customer_id}
Update a customer
updateCustomer 1 param body → 200401404
DELETE
/customers/{customer_id}
Delete a customer
deleteCustomer 1 param → 200401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are CustomerInput (7 properties), DeleteResponse (3 properties), Error (1 property). Each schema is shown below with its type and property counts.

DeleteResponse
object
3 properties
Customer
CustomerInput
object
7 properties
Error
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tap-payments-customers-api-openapi.yml Raw ↑

Other APIs Tap Payments publishes across the network.

Tap Payments Webhooks
Tap Payments Authorize API
Tap Payments Business API
Tap Payments Cards API
Tap Payments Charges API
Tap Payments Invoices API
Tap Payments Payouts API
Tap Payments Refunds API
Tap Payments Tokens API