Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.telegent.com/llms.txt

Use this file to discover all available pages before exploring further.

Goal: Get the partner into the dev environment with credentials, console access, and a working OAuth token.

​
Checklist

#TaskOwner
1Telegent account created and DID (Distributor ID) assigned.Telegent
2AccountKey (DID-…) and AccountSecret issued via secure channel.Telegent
3MVNO Console login provisioned for primary technical contact.Telegent
4Partner confirmed access to docs.telegent.com (partner-facing API docs).Partner
5Partner accessed Swagger at https://api.telegent.com/docs/index.html (interactive API explorer).Partner
6Partner imported Postman collection (optional — Swagger covers most cases).Partner
7Partner generated first OAuth token successfully against /v1.0/oauth2/tokens.Partner
8Partner reviewed escalation contacts and on-call paths.Partner

​
Generating Your First Token

Endpoint: POST /v1.0/oauth2/tokens
Request
{
  "AccountKey": "YOUR_ACCOUNT_KEY",
  "AccountSecret": "YOUR_ACCOUNT_SECRET",
  "ApiEndpoint": "https://api.telegent.com/v1.0/numbers/provision"
}
Response
{
  "token": "abcdefghi.................",
  "successful": true,
  "tokenExpiry": "05/02/2026 06:36:13 PM"
}
Token reminder: Tokens are scoped to a specific ApiEndpoint and expire after a few minutes — always include AccountKey, AccountSecret, and ApiEndpoint in every token request. Never share credentials over email.
Phase complete when: Partner can sign into the console, hit the dev API, and generate a valid token on their own.

Previous: Discovery & Setup

POC kickoff and NDA

Next: Phase 2 — Connectivity

Configure webhooks and SIP interconnect