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

Kushki Tokens API

Card tokenization (client-side via Kushki.js, returns a one-time transactionToken)

Kushki Tokens API is one of 12 APIs that Kushki publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Tokens. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a JSON-LD context, and 2 JSON Schemas.

This API exposes 1 operation across 1 path, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: https://api.kushkipagos.com, https://api-uat.kushkipagos.com, https://api-stg.kushkipagos.com.

1 operations 1 paths 3 schemas 1 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.kushkipagos.com
Authentication
API Key, API Key
Contact
Resource Areas
1

Authentication & Security 2

Kushki Tokens API declares 2 security schemes for authenticating requests. An API key is passed in the header as Public-Merchant-Id (PublicMerchantId). An API key is passed in the header as Private-Merchant-Id (PrivateMerchantId). By default, every request must be authenticated.

  • PublicMerchantId — Client-side merchant key. Used by Kushki.js and mobile SDKs to tokenize cards. Never use server-side for charging.
  • PrivateMerchantId — Server-side merchant key. Required for charge, capture, void, refund, subscription, and payout calls.

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.

Tokens 1

Card tokenization (client-side via Kushki.js, returns a one-time transactionToken)

POST
/card/v1/tokens
Kushki Tokenize Card
createCardToken body → 2004XX

Schemas 3

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

Error
object
2 properties
TokenResponse
object
1 property
TokenRequest
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kushki-tokens-api-openapi.yml Raw ↑

Other APIs Kushki publishes across the network.

Kushki Subscriptions API
Kushki Payouts API
Kushki Webhooks
Kushki Branches API
Kushki Card Present Charges API
Kushki Cash API
Kushki Charges API
Kushki Pre-Authorization API
Kushki Terminals API
Kushki Transfer API
Kushki Voids and Refunds API
Where this information came from

This is an independent, third-party profile of Kushki Tokens 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.