How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

TabaPay Key API

This resource represents an RSA Encryption Key.

TabaPay Key API is one of 16 APIs that TabaPay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Key. 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 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://{FQDN}:{PORT}.

3 operations 2 paths 8 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.tabapay.com
Authentication
HTTP Bearer, API Key
License
All rights reserved
Resource Areas
1

Authentication & Security 2

TabaPay Key API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as Authorization (custom-header). By default, every request must be authenticated.

Paths & Operations 3

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

Key 3

This resource represents an RSA Encryption Key.

POST
/v1/clients/{ClientID}/keys
Create Key
keyCreate 1 param body → 200429
DELETE
/v1/clients/{ClientID}/keys/{KeyID}
Delete Key
keyDelete 3 params → 200404410
GET
/v1/clients/{ClientID}/keys/{KeyID}
Retrieve Key
keyRetrieve 3 params → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are createKeyResponse (9 properties), retrieveKeyResponse (7 properties), apiResponseSCECEM (3 properties), apiResponseSCEC (2 properties). Each schema is shown below with its type and property counts.

apiResponseSCECEM
object
3 properties
retrieveKeyResponse
object
7 properties
SC
integer
[HTTP Status Code](https://developers.tabapay.com/reference/http-status-codes/)
EM
string
Short description of the error if an error occurred.
EC
string
Internal Error Code. This is used to help TabaPay team members trace an error.
createKey
object
1 property 1 required
createKeyResponse
object
9 properties
apiResponseSCEC
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tabapay-key-api-openapi.yml Raw ↑

Other APIs TabaPay publishes across the network.

TabaPay 3D Secure API
TabaPay Account API
TabaPay Bank API
TabaPay Card API
TabaPay Client API
TabaPay FXRate API
TabaPay Health API
TabaPay Ledger API
TabaPay OFAC API
TabaPay SubClient API
TabaPay Tag API
TabaPay Transaction API
Where this information came from

This is an independent, third-party profile of TabaPay Key API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.