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

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.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.cable.tech, https://transaction-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.2.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), UpdateTransactionScreeningRequest (8 properties), TransactionScreening (8 properties). Each schema is shown below with its type and property counts.

WriteOperationResponse
object
4 properties 4 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.
NewScreeningRequest
array
Screening data to add.
Screening_checkScreening_Response_200
object
4 properties
GeneralErrorErrorsItems
object
2 properties
GeneralError
object
3 properties 2 required
NewScreeningRequestItems
object
10 properties 6 required
NewScreeningRequestItemsType
string
The type of screening check performed (e.g., SANCTION, PEP, ADVERSEMEDIA, etc.).
Screening
object
10 properties 3 required
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…
ScreeningType
string
The type of screening check performed (e.g., SANCTION, PEP, ADVERSEMEDIA, etc.).
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…
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
NewTransactionScreeningRequestItems
object
8 properties 6 required
Screening_checkTransactionScreening_Response_200
object
4 properties
NewTransactionScreeningRequest
array
Transaction screening data to add.
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
AdditionalPropertiesType
string
The type of the additional property value, for example "string", "number", "boolean", "object", "array".

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
Where this information came from

This is an independent, third-party profile of Cable screening 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.