Telesign · Authentication Profile
Telesign Authentication
Authentication
Telesign secures its APIs with http and apiKey across 3 declared security schemes, as derived from its OpenAPI definitions.
AuthenticationCommunicationsFraud PreventionPhone IntelligenceSMSVerificationTelecommunicationsMessagingVoiceEmail IntelligenceIdentityNumber MaskingAccount
Methods: http, apiKey
Schemes: 3
OAuth flows:
API key in: header
Security Schemes
Basic http
scheme: basic
Digest apiKey
· in: header ()
bearerAuth http
scheme: bearer
Source
Authentication Profile
generated: '2026-10-07'
method: searched
source: https://developer.telesign.com/enterprise/docs/authentication (read as markdown twin 2026-10-07), https://developer.telesign.com/enterprise/docs/authenticate-callbacks, https://developer.telesign.com/enterprise/page/sdks, securitySchemes of the 21 published OpenAPI files under openapi/
docs: https://developer.telesign.com/enterprise/docs/authentication
summary:
types:
- http
- apiKey
api_key_in:
- header
credentials: Customer ID and API Key, issued in the Telesign portal; the SDKs apply Digest where supported and fall back to Basic.
schemes:
- name: Basic
type: http
scheme: basic
description: 'HTTP Basic authentication: the Customer ID as the user name and the API Key as the password, base64-encoded in the Authorization header. The docs call it "easiest to implement" and it is accepted by every published contract except the Flow Builder and Protect Platform APIs.'
docs: https://developer.telesign.com/enterprise/docs/authentication#basic-authentication
sources:
- openapi/telesign-accounts-api-openapi.yml
- openapi/telesign-app-verify-api-openapi.yml
- openapi/telesign-deactivated-numbers-api-openapi.yml
- openapi/telesign-detect-api-openapi.yml
- openapi/telesign-email-intelligence-api-openapi.yml
- openapi/telesign-email-intelligence-extended-response-openapi.yml
- openapi/telesign-engage-api-number-masking-openapi.yml
- openapi/telesign-engage-api-openapi.yml
- openapi/telesign-engage-api-voice-openapi.yml
- openapi/telesign-intelligence-cloud-api-openapi.yml
- openapi/telesign-legacy-phone-id-api-openapi.yml
- openapi/telesign-silent-verify-api-openapi.yml
- openapi/telesign-smart-verify-api-openapi.yml
- openapi/telesign-sms-verify-api-openapi.yml
- openapi/telesign-verify-api-openapi.yml
- openapi/telesign-voice-verify-api-openapi.yml
- name: Digest
type: apiKey
in: header
header: Authorization
description: 'Telesign''s own HMAC request-signing scheme (not RFC 7616): the client builds a string-to-sign from the HTTP method, content type, date (Date or x-ts-date), x-ts-auth-method, x-ts-nonce and the resource path, signs it with the base64-decoded API Key using HMAC-SHA256 (HMAC-SHA1 also accepted), and sends "Authorization: TSA {Customer ID}:{signature}". Recommended for production; the SDKs implement it.'
docs: https://developer.telesign.com/enterprise/docs/authentication#digest-authentication
headers:
- Authorization
- x-ts-date
- x-ts-auth-method
- x-ts-nonce
sources:
- openapi/telesign-app-verify-api-openapi.yml
- openapi/telesign-deactivated-numbers-api-openapi.yml
- openapi/telesign-detect-api-openapi.yml
- openapi/telesign-email-intelligence-api-openapi.yml
- openapi/telesign-email-intelligence-extended-response-openapi.yml
- openapi/telesign-engage-api-openapi.yml
- openapi/telesign-intelligence-cloud-api-openapi.yml
- openapi/telesign-smart-verify-api-openapi.yml
- openapi/telesign-sms-verify-api-openapi.yml
- openapi/telesign-verify-api-openapi.yml
- name: bearerAuth
type: http
scheme: bearer
description: Bearer access token for the Protect Platform (Flow Builder). The token is obtained from POST /authenticationmanager/v1/authenticate/api on us-east-1.di-platform.telesign.com (operationId initiateAuthentication) and sent as "Bearer YOUR_ACCESS_TOKEN_HERE" to us-east-1.di-hub.telesign.com.
docs: https://developer.telesign.com/enterprise/reference/initiateauthentication
sources:
- openapi/telesign-flow-builder-api-openapi.yml
- openapi/telesign-protect-platform-api-openapi.yml
callback_authentication:
description: Telesign signs every callback it sends with HMAC-SHA256 over the request body using the customer's base64-decoded API Key; the signature is sent in both the Authorization header ("TSA {Customer ID}:{signature}") and X-TS-Authorization. Receivers recompute and compare the signature.
docs: https://developer.telesign.com/enterprise/docs/authenticate-callbacks
headers:
- Authorization
- X-TS-Authorization
algorithm: HMAC-SHA256
oauth2: false
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/telesign-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.