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

The Transactions API from Tribe Payments — 2 operation(s) for transactions.

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

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

2 operations 2 paths 21 schemas 2 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 Transactions API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-auth-report-api-key (apiKey). An API key is passed in the header as x-auth-report-api-password (apiPassword). By default, every request must be authenticated.

Paths & Operations 2

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

Transactions 2
POST
/registered-transactions-address
posttransactions body → 200
POST
/transactions
posttransactions body → 202400401403422429

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are TransactionsRecordsP2p (33 properties), TransactionsRecordsTransaction (18 properties), TransactionsRecordsSettlement (16 properties), TransactionsRecordsCustomer (9 properties). Each schema is shown below with its type and property counts.

TransactionsRecordsCustomer
object
9 properties 8 required
Transactions
object
6 properties 4 required
TransactionsRecordsP2p
object
33 properties 32 required
TransactionsRecordsSettlement
object
16 properties 16 required
TransactionsRecordsTransaction
object
18 properties 18 required
TransactionsRecords
object
6 properties
TransactionsRecordsCard
object
3 properties 3 required
TransactionsRecordsCompany
object
2 properties 2 required
TransactionsWebhook
object
2 properties 2 required
Transactions_2
object
3 properties
violationObjectForbidden
object
2 properties
responseSuccess
object
1 property
violationObjectTooManyRequests
object
2 properties
unprocessableContent
object
2 properties
responseUnauthorized
object
3 properties
TransactionsSettlement
object
2 properties
TransactionsTransaction
object
3 properties
responseForbidden
object
3 properties
responseErrorTransactions
object
3 properties
violationObjectTransactions
object
2 properties
responseTooManyRequests
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tribe-payments-transactions-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 Transactions 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.