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

Cable screening API

The screening API from Cable — 2 operation(s) for screening.

Cable screening API is one of 20 APIs that Cable publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include screening. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 2 paths, and defines 19 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api.cable.tech.

6 operations 2 paths 19 schemas 2 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.cable.tech
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Cable screening API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). It accepts HTTP bearer tokens (BearerAuth).

Paths & Operations 6

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

screening 6
GET
/v2/screening
Check if a screening exists
check-screening 2 params → 200401404429500
POST
/v2/screening
Add new screening(s)
add-screening 1 param body → 201400401409429500
PUT
/v2/screening
Update screenings in batch
update-screenings 1 param body → 200400401404429500
GET
/transaction_screening
Check if a transaction screening exists
check-transaction-screening 2 params → 200401404429500
POST
/transaction_screening
Add new transaction screening(s)
add-transaction-screening 1 param body → 201400401409429500
PUT
/transaction_screening
Update an existing transaction screening
update-transaction-screening 1 param body → 200400401404429500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are Screening (10 properties), NewScreeningRequestItems (10 properties), TransactionScreening (8 properties), UpdateTransactionScreeningRequest (8 properties). Each schema is shown below with its type and property counts.

GeneralErrorErrorsItems
object
2 properties
Screening
object
10 properties 3 required
NewScreeningRequestItems
object
10 properties 6 required
NewTransactionScreeningRequest
array
Transaction screening data to add.
NewScreeningRequest
array
Screening data to add.
ScreeningOutcome
string
The outcome of the screening check (e.g., POSITIVE, NEGATIVE, TRUEPOSITIVE, etc.). The value "SCREENED" should only be used when the outcome is not available b…
UpdateTransactionScreeningRequest
object
Transaction screening data to update, referenced by 'sarid'. The 'timestamp' field represents the update time. Only the fields to be updated need to be include…
8 properties 2 required
NewScreeningRequestItemsType
string
The type of screening check performed (e.g., SANCTION, PEP, ADVERSEMEDIA, etc.).
ScreeningType
string
The type of screening check performed (e.g., SANCTION, PEP, ADVERSEMEDIA, etc.).
NewTransactionScreeningRequestItems
object
8 properties 6 required
UpdateScreeningsRequest
array
Screening data to update, referenced by 'screeningid'. The 'timestamp' field represents the update time. Only the fields to be updated need to be included.
AdditionalPropertiesType
string
The type of the additional property value, for example "string", "number", "boolean", "object", "array".
Screening_checkTransactionScreening_Response_200
object
4 properties
TransactionScreening
object
8 properties 2 required
AdditionalProperties
object
Additional metadata that can be added to a payload, such as transaction checks, alerts, and suspicious activities.
4 properties 4 required
GeneralError
object
3 properties 2 required
WriteOperationResponse
object
4 properties 4 required
Screening_checkScreening_Response_200
object
4 properties
NewScreeningRequestItemsOutcome
string
The outcome of the screening check (e.g., POSITIVE, NEGATIVE, TRUEPOSITIVE, etc.). The value "SCREENED" should only be used when the outcome is not available b…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cable-screening-api-openapi.yml Raw ↑

Other APIs Cable publishes across the network.

Cable alerts API
Cable authentication API
Cable business API
Cable checks API
Cable company API
Cable customerSar API
Cable helper API
Cable identityVerification API
Cable onboardingFlow API
Cable person API
Cable retail API
Cable riskAssessment API