Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Risk Monitor - Client API

Tribe Payments Risk Monitor Client API (v1.1) for real-time fraud and transaction-risk monitoring, letting clients submit and query risk decisions, with a webhooks interface for risk event notifications. Harvested verbatim from the Tribe developer portal.

Risk Monitor - Client API is one of 15 APIs that Tribe Payments publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments, Fraud, Risk Management, Transaction Monitoring, and United Kingdom. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 5 operations across 4 paths, organized into 3 resource areas, and defines 11 schemas. It is described by OpenAPI 3.0.3, at version 0.0.0.

Requests are made against a single base URL, /.

5 operations 4 paths 11 schemas 1 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.0.0
Server
/
Authentication
API Key, API Key
Resource Areas
3

Authentication & Security 2

Risk Monitor - Client 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 5

Across 4 paths, the API surfaces 5 operations — 1 GET, 1 PATCH, 3 POST. They span 3 resource areas: Event Data, User Actions Trigger, Health Check. Each is listed below with its method, path, parameters, and response codes.

Event Data 3
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
User Actions Trigger 1
POST
/v1/events/{eventId}/data/{identifier}/trigger-user-actions/{actionId}
Triggers action for the event data
subresource_postTrigerUserActionsForEventDataItem 3 params body → 204400401404409415422500
Health Check 1
POST
/v1/health-check
Performs system health check
postHealthCheckCollection body → 200400401415500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Event.EventDataResponseDto (11 properties), UnprocessableEntityErrorResponseDto (4 properties), ViolationDto (3 properties), InternalServerErrorResponseDto (3 properties). Each schema is shown below with its type and property counts.

Event.EventDataResponseDto
object
11 properties
EventDataTagDto
object
2 properties
EventDataActionDto
object
3 properties
BadRequestErrorResponseDto
object
3 properties 3 required
UnauthorizedErrorResponseDto
object
3 properties 3 required
NotFoundErrorResponseDto
object
3 properties 3 required
ConflictErrorResponseDto
object
3 properties 3 required
UnsupportedMediaTypeErrorResponseDto
object
3 properties 3 required
InternalServerErrorResponseDto
object
3 properties 3 required
UnprocessableEntityErrorResponseDto
object
4 properties 4 required
ViolationDto
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tribe-payments-trb-risk-monitor-client-api-openapi.json Raw ↑

Other APIs Tribe Payments publishes across the network.

Payment Gateway - Credit Card API
Payment Gateway - Hosted Payments API (HPP)
Payment Gateway - Credit Card Token API
Payment Gateway - Reports API
Point of Sale - Device Directory API
Open Banking - Bank API
Open Banking - Third-Party Providers API (TPP)
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)