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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
TMT ID

TMT ID Authenticate API

Authenticate user with MNO or OTP. These endpoints can be directly called by the users.

Documentation Provider Profile APIs.io OpenAPI GitHub

TMT ID Authenticate API is one of 8 APIs that TMT ID publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authenticate. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.1.2.

Requests are made against 2 base URLs: https://auth-staging-api.tmtid.dev/v1, https://auth-api.tmtanalysis.com/v1.

3 operations 3 paths 9 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.2
Base URL
https://api.tmtverify.com
Authentication
HTTP Basic, HTTP Bearer
Contact
TMT Support
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

TMT ID Authenticate API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basic). It accepts HTTP bearer tokens (paseto_token).

Paths & Operations 3

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

Authenticate 3

Authenticate user with MNO or OTP. These endpoints can be directly called by the users.

POST
/oauth/token
This phase is where the Customer requests authorization to perform an authentication for a given device.
getAccessToken body → 200400401503
POST
/get_config
The getconfig endpoint will return specific instructions on how to begin the session with the relevant MNO and how to send the OTP message.
getConfig body → 200400401
POST
/validate
The validate endpoint will return whether the phone number was validated successfully or not and the service used in order to achieve the authentication.
validateUserSession body → 200400

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are AuthorizationUri (5 properties), GetResult (5 properties), GetAuthUrl (4 properties), ValidateResponse (3 properties). Each schema is shown below with its type and property counts.

AuthorizeRequestConfig
VendorAuthorizationConfig
object
2 properties
AuthRequest
object
2 properties 2 required
ErrorResponse
object
2 properties 2 required
GetAuthUrl
object
4 properties 2 required
GetResult
object
5 properties 1 required
AuthResponse
object
3 properties 3 required
ValidateResponse
object
3 properties 2 required
AuthorizationUri
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tmt-id-authenticate-api-openapi.yml Raw ↑

Other APIs TMT ID publishes across the network.

TMT ID HTTP API
AE Profile APIs.io
TMT ID HTTP API v1.3 API
AE Profile APIs.io
TMT ID HTTP API v2.0 API
AE Profile APIs.io
TMT ID Network Biometrics API
AE Profile APIs.io
TMT ID Service API
AE Profile APIs.io
TMT ID Standard API Call API
AE Profile APIs.io
TMT ID v2 (deprecated) API
AE Profile APIs.io
#Authenticate
← Back to T APIs
API Details
ID
tmt-id:tmt-id-authenticate-api
Base URL
https://api.tmtverify.com
Docs
https://tmtid.com/developer/tmt_verify_v1.html
Provider
TMT ID
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=tmt-id-authenticate-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/tmt-id-authenticate-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of TMT ID Authenticate 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.