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 Charges API

Charge a card or other payment source.

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

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

4 operations 2 paths 8 schemas 2 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 Charges 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 4

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

Charges 4

Charge a card or other payment source.

POST
/charges
Create a charge
createCharge body → 200400401
GET
/charges
List all charges
listCharges → 200401
GET
/charges/{charge_id}
Retrieve a charge
retrieveCharge 1 param → 200401404
PUT
/charges/{charge_id}
Update a charge
updateCharge 1 param body → 200401404

Schemas 8

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

Redirect
object
1 property
Source
object
The payment source. Provide a token id, a saved card id, an authorize id (to capture), or a scheme identifier such as srckw.knet, srcsa.mada, srcbh.benefit, sr…
1 property
Customer
Charge
object
11 properties
CustomerInput
object
7 properties
ChargeInput
object
13 properties 3 required
ChargeList
object
1 property
Error
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tap-payments-charges-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 Customers API
Tap Payments Invoices API
Tap Payments Payouts API
Tap Payments Refunds API
Tap Payments Tokens API