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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Tribe Payments

Tribe Payments Event Data API

The Event Data API from Tribe Payments — 6 operation(s) for event data.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 7 operations across 6 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 0.0.0.

Requests are made against a single base URL, /.

7 operations 6 paths 22 schemas 1 GET1 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.0
Server
/
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Tribe Payments Event Data API declares 2 security schemes for authenticating requests. An API key is passed in the header as bearer (Bearer). An API key is passed in the header as X-AUTH-TOKEN (Token). By default, every request must be authenticated.

  • Bearer — Value for the bearer header parameter.
  • Token — Value for the X-AUTH-TOKEN header parameter.

Paths & Operations 7

Across 6 paths, the API surfaces 7 operations — 1 GET, 1 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Event Data 7
POST
/v1/events/{eventId}/data
Creates event data
subresource_postEventDataCollection 1 param body → 204400401404415422500
GET
/v1/events/{eventId}/data/{identifier}
Retrieves event data
data_get_for_clientEventItem 2 params → 200401404500
PATCH
/v1/events/{eventId}/data/{identifier}
Updates event data
subresource_patchEventDataItem 2 params body → 204400401404415422500
POST
/registered-summary-web-hook-address
Summary
webhook_send_summary 1 param body → 200
POST
/registered-system-action-web-hook-address
System action
webhook_send_system_action 1 param body → 200
POST
/registered-user-action-web-hook-address
Operator action
webhook_send_operator_action 1 param body → 200
POST
/registered-recurring-action-web-hook-address
Recurring action
webhook_send_recurring_action 1 param body → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are Event.EventDataResponseDto (11 properties), Webhook.UserActionPayloadDto (8 properties), Webhook.SystemActionPayloadDto (7 properties), Webhook.RecurringActionPayloadDto (7 properties). Each schema is shown below with its type and property counts.

EventDataActionDto
object
3 properties
BadRequestErrorResponseDto
object
3 properties 3 required
UnprocessableEntityErrorResponseDto
object
4 properties 4 required
InternalServerErrorResponseDto
object
3 properties 3 required
NotFoundErrorResponseDto
object
3 properties 3 required
UnsupportedMediaTypeErrorResponseDto
object
3 properties 3 required
Event.EventDataResponseDto
object
11 properties
EventDataTagDto
object
2 properties
ViolationDto
object
3 properties 3 required
UnauthorizedErrorResponseDto
object
3 properties 3 required
ActionHitDto
object
3 properties 3 required
Webhook.EventDataSummaryPayloadDto
object
6 properties 4 required
Webhook.RecurringActionPayloadDto
object
7 properties 5 required
ActionHitDataCustomDto
object
Additional parameters that should be sent with a webhook. The result depends on the action setup.
EventDto
object
2 properties 2 required
Webhook.UserActionPayloadDto
object
8 properties 5 required
ActionHitDataDto
object
Data object that contains changeset.
2 properties 2 required
ActionHitDataChangeSetDto
object
Changes made after the action hit. The result depends on the action setup.
ActionHitActionDto
object
Object of the action that was hit.
5 properties 5 required
TriggeredByDto
object
2 properties 2 required
Webhook.SystemActionPayloadDto
object
7 properties 5 required
EventTagDto
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tribe-payments-event-data-api-openapi.yml Raw ↑

Other APIs Tribe Payments publishes across the network.

Issuer Processor - Program Manager API (PM API)
AE Profile APIs.io
Issuer Processor - Transaction Authorization Interface (TAI API)
AE Profile APIs.io
Acquiring Processor - Acquirer API (ACAPI)
AE Profile APIs.io
Acquiring Processor - Merchant API (MAPI)
AE Profile APIs.io
Acquiring Processor - Terminal API (TAPI)
AE Profile APIs.io
Acquiring Processor - Tokenization API (TOKAPI)
AE Profile APIs.io
Bank Connect - Payment Services API
AE Profile APIs.io
Tribe Payments 3DS authentication required API
AE Profile APIs.io
Tribe Payments Account API
AE Profile APIs.io
Tribe Payments Accounts API
AE Profile APIs.io
Tribe Payments App API
AE Profile APIs.io
Tribe Payments Authorization API
AE Profile APIs.io
#Event Data
← Back to T APIs
API Details
ID
tribe-payments:tribe-payments-event-data-api
Server
/
Docs
https://doc.tribepayments.com/docs/trb-gateway--credit-card-api--v3
Provider
Tribe Payments
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=tribe-payments-event-data-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/tribe-payments-event-data-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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