Telesign Protect API Authentication API

The Protect API Authentication API from Telesign — 1 operation(s) for protect api authentication.

Operations 1

POST /authenticationmanager/v1/authenticate/api Generate access token #

Documentation

Specifications

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-initiate-av-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-200-av-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-finalize-av-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-caller-id-av-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-get-av-status-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-get-phone-id-live-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-post-email-idrequest-body-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-post-phone-idrequest-body-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-post-score-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-post-email-int-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-num-mask-inputs-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-omni-req-details-for-rcs-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-omni-req-details-for-viber-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-omni-req-details-for-wa-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-post-smssuccess-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-put-completion-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-omni-req-channel-obj-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-recording-with-detail-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-recording-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-action-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-get-phone-id-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-get-phone-id-ndresponse-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-svresponse-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-score-numbering-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-shared-response-schema-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-carrier-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-score-phone-type-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-get-status-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-simswap-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-post-verification-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-get-verification-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-post-verification-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-patch-verification-state-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-patch-verification-state-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/telesign/refs/heads/main/json-schema/telesign-send-voice-code-response-schema.json

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/telesign:telesign-protect-api-authentication-api"
All apis
curl "https://apis.io/api/v1/apis?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.

OpenAPI Specification

telesign-protect-api-authentication-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Protect Platform Protect API Authentication API
  version: '1.0'
  description: Use this API to initiate authentication for the Protect Platform API.
  contact:
    name: Telesign Customer Support Team
    email: support@telesign.com
servers:
- url: https://us-east-1.di-platform.telesign.com
tags:
- name: Protect API Authentication
paths:
  /authenticationmanager/v1/authenticate/api:
    parameters: []
    post:
      summary: Generate access token
      operationId: initiateAuthentication
      responses:
        '200':
          description: '**Success.** The request was processed successfully.


            | Status | Condition | error.message | Description |

            | --- | --- | --- | --- |

            | Success | — | The request was processed successfully. |'
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Describes the results of the authentication request.
                    example: Operation completed successfully.
                  data:
                    type: object
                    description: 'Contains properties related to the the access token. '
                    properties:
                      accessToken:
                        type: string
                        description: 'Access token to be used in `Authorization: Bearer`. Must be used in all subsequent API requests.'
                        example: YOUR_ACCESS_TOKEN_HERE
                      expirationTimeSeconds:
                        type: integer
                        description: 'The validity of the token, measured in seconds. '
                        example: 28800
              examples:
                Response:
                  value:
                    message: Operation completed successfully.
                    data:
                      accessToken: YOUR_ACCESS_TOKEN_HERE
                      expirationTimeSeconds: 28800
        '400':
          description: "**Request validation failed.** One or more fields are missing or have the wrong type/format. See `errors.description` for more details.\n\nStatus Condition | error.message  | Description\n------------|---------------------|------------------------------\nMalformed JSON/body fields  | `Request validation failed`         | One or more fields are missing or have the wrong type/format. See `errors.description` for a per-field breakdown.                                           \n"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/tokenResponse'
              examples:
                Validation errors:
                  value:
                    errors:
                    - name: The authorization field is required.
                      description: One or more validation errors occurred.
        '401':
          description: "**Authorization Errors.** The authentication request failed because the token was invalid, expired, couldn't be validated or because no authorization header was provided. \n\nStatus Condition | error.message  | Description\n------------|---------------------|------------------------------\nToken failed validation  | Error validating token         | Token could not be parsed or verified.                                           \nProduct failed validation | Error validating token access to product | Credentials have no access to the product.                                                           \nNo Authorization header | No authorization header provided | Authentication header is completely absent.  \nToken expired / not found | Invalid or expired token | Token is syntactically valid but expired or no longer accepted."
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/tokenResponse'
              examples:
                Incorrect API key:
                  value:
                    errors:
                    - name: Unauthorized
                      description: Incorrect api key
                Invalid authorization header:
                  value:
                    errors:
                    - name: Unauthorized
                      description: Invalid authorization header
                Invalid credentials:
                  value:
                    errors:
                    - name: Unauthorized
                      description: API Credentials do not exist, check that credentials are suitable for this product
        '404':
          description: '**Unknown path.** The requested resource or endpoint does not exist. Invalid Path or endpoint requested, the API returns an error.


            Status Condition | error.message  | Description

            ------------|---------------------|----------------

            Unknown path | `Endpoint not found` | The requested resource or endpoint does not exist.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/tokenResponse'
              examples:
                Endpoint not found:
                  value:
                    errors:
                    - name: Unknown path
                      description: The requested resource or endpoint does not exist
        '500':
          description: '**Internal error.** Unexpected exception on the server side.


            Status Condition | error.message  | Description

            ------------|---------------------|----------------

            Internal error | Internal Server Error | Unexpected exception on the server side.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/tokenResponse'
              examples:
                Internal server error:
                  value:
                    errors:
                    - name: Internal Server Error
                      description: Unexpected exception on the server side
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                productId:
                  type: integer
                  default: 3
                  description: The Product ID associated with the Flow Builder. The Product Id for the Flow Builder is `3`.
            examples:
              Authentication request:
                value:
                  productId: 3
        description: ''
      description: '> 📘 NOTE:

        >

        > Select regional availability. This feature is currently available for customers with end users in select countries. To find out if this feature is available in your region, contact a Telesign expert. This product is available for full-service accounts only.


        Use this endpoint to generate an access token to interact securely with Protect Platform services, which require an external authentication service that issues an access token upon successful validation of an API Key.


        Send credentials via Basic Auth ("Authorization: Basic ...") together with "x-API-key". After you send a POST request to the authentication service with the required credentials, the service returns a Bearer token, which must be included in the Authorization header of all subsequent API requests to ensure secure access. If your access token expires, you must re-authenticate using this endpoint to obtain a new token. Include the accessToken in the Authorization header of every API request for authentication and authorization.


        ## General requirements

        * **Authentication:** [Basic]

        * **Encoding:** Accepts only **UTF-8 unicode** characters as inputs.

        * **Accepts:** `application/json`

        * **Responds with:** `application/json`

        * **Required headers:**

        * `Content-Type: application/json`

        * `x-API-key: [YOUR_API_KEY_HERE]`'
      parameters:
      - schema:
          type: string
        in: header
        name: Authorization
        description: Your credentials encoded in Base64 (e.g., Basic YOUR_BASE64_ENCODED_CREDENTIALS)
        required: true
      - schema:
          type: string
        in: header
        name: x-API-key
        description: The API Key associated with your account. (e.g., YOUR_API_KEY_HERE)
        required: true
      - schema:
          type: string
        in: header
        name: Content-Type
        description: Must be set to application/json.
        required: true
      tags:
      - Protect API Authentication
components:
  schemas:
    tokenResponse:
      title: tokenResponse
      type: object
      x-examples: {}
      properties:
        errors:
          type: array
          items:
            type: object
            properties:
              name:
                type: string
                description: The error returned by the API.
              description:
                type: string
                description: A description of an error returned by the API.
x-readme:
  explorer-enabled: true
  proxy-enabled: true
  samples-enabled: true