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

Tribe Payments Prepare API

The Prepare API from Tribe Payments — 1 operation(s) for prepare.

Tribe Payments Prepare API is one of 45 APIs that Tribe Payments publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Prepare. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against a single base URL, http://127.0.0.1:10010/v3.

1 operations 1 paths 12 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.0
Server
http://127.0.0.1:10010/v3
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Tribe Payments Prepare API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-auth-account-id (accountId). An API key is passed in the header as x-auth-account-password (accountPassword). By default, every request must be authenticated.

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.

Prepare 1
POST
/prepare
postprepare body → 202400401403

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are PrepareCustomer (12 properties), PrepareSettings (11 properties), PrepareTransaction (4 properties), Prepare (4 properties). Each schema is shown below with its type and property counts.

violationObjectForbidden
object
2 properties
PrepareRecurring
object
3 properties
responseSuccess
object
1 property
PrepareCustomer
object
12 properties
responseUnauthorized
object
3 properties
PrepareTransaction
object
4 properties 4 required
responseError
object
3 properties
PrepareSettings
object
11 properties 1 required
Prepare
object
4 properties
responseForbidden
object
3 properties
violationObject
object
3 properties
PrepareSettingsCustomerEmailNotification
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tribe-payments-prepare-api-openapi.yml Raw ↑

Other APIs Tribe Payments publishes across the network.

Issuer Processor - Program Manager API (PM API)
Issuer Processor - Transaction Authorization Interface (TAI API)
Acquiring Processor - Acquirer API (ACAPI)
Acquiring Processor - Merchant API (MAPI)
Acquiring Processor - Terminal API (TAPI)
Acquiring Processor - Tokenization API (TOKAPI)
Bank Connect - Payment Services API
Tribe Payments 3DS authentication required API
Tribe Payments Account API
Tribe Payments Accounts API
Tribe Payments App API
Tribe Payments Authorization API
Where this information came from

This is an independent, third-party profile of Tribe Payments Prepare 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.