Skip to main content
Every request to the Telnyx API is decided on the same questions, whatever product it reaches.
  • Who is acting. A principal, proven by a credential.
  • What it wants to do. An action, one per API operation.
  • Which resource, and its project. Preview
  • In what context, such as the source IP or how the principal signed in. Preview

Core Concepts

One Request

The owner configures IAM before any request. At request time, Telnyx runs its checks in a fixed order at the edge of the Telnyx API, and the first refusal answers the request, so a refused request never reaches the product. The example follows the release pipeline from the Quick Start through two requests. Assigning a number is allowed, because its role allows number.update. Editing a SIP connection is refused at IAM, because no role allows connection.update. For users, the permission groups set in Mission Control Portal still apply as well, inside the product and on the categories it checks, until they retire. Service accounts, like this pipeline, are decided by their roles alone.

Outside IAM

IAM leaves some things to other systems on purpose.
  • Product credentials. SIP credentials, WebRTC tokens, Cloud Storage access keys, and Edge Compute bindings stay with their products.
  • Webhooks. IAM governs requests to Telnyx. Webhooks Telnyx sends are signed separately.
  • Entitlement and billing. What an organization can buy or use is set by its account level, and billing ownership does not change.
  • Configuration rules. A role allows or denies actions. It does not inspect what a request sets, such as a number’s country.
  • Assuming identities. Nobody signs in as a role, and nobody works as another person. A manager works in a managed organization as themselves.