Skip to main content
Endpoint pages in the API reference do not all carry the same sample treatment: short pages show every supported language for every operation, and long pages show the full set for the operations you reach first, then the two most-used forms for the rest. This page is the definition of which pages get which treatment. For how the samples themselves are written — the dependency-free idioms per language and the response envelope rules — see How request samples work (cURL + 5 SDK languages).

​
The two treatments

A page with 15 or fewer operations renders the full six-language sample group — cURL, Node.js (TypeScript), Python, Go, Ruby, and PHP, in that fixed order — for every operation. Nothing trims. A page with more than 15 operations renders the full group for its first 15 operations, and cURL + TypeScript for every operation after the fifteenth. Hero flows past the cut still get the full-group treatment inside a Worked sequences section further down the page. The 15-operation count is fixed, so new operations slot in before the fifteenth and keep the full set — nothing rebalances as the catalogue grows.

​
The floor that never changes

Either way, two rules hold on every request sample:
  1. cURL and Node.js (TypeScript) are always present — the two most-used forms are promised on every sample, trimmed or not.
  2. Long-page hero flows get the full group in place — nav hints on pages past the cut step you down to a Worked sequences section where the six-language group lives.
Here is the floor demonstrated on an operation at, or past, the trim cut — cURL and TypeScript in one group, and nothing less:
Any language past the pair — Python, Go, Ruby, PHP — is additive; the guarantee you can rely on when skimming or scripting is the pair itself.

​
A long page, worked end to end

The Settings page is the split in action — 54 operations on one page, across the group editor, sender, and keyword-rule surfaces:
  1. The first 15 operations carry the full group. Every operation up to the fifteenth — the editor surfaces that open the page — renders cURL, Node.js (TypeScript), Python, Go, Ruby, and PHP.
  2. Operations past the fifteenth carry cURL + TypeScript. The settings walk-throughs — keyword rules, opt-out rules, sender identities, and the administrative surfaces behind them — show the pair and nothing more, which keeps a 54-operation page scannable.
  3. Hero flows rerun in full. An operation past the cut still gets the full-group treatment when it anchors a walk-through: an in-page hint points you to the Worked sequences section lower on the page, where the end-to-end flows render every block in all six languages.
The Settings page ships exactly this shape — copy it on any page past the 15-operation cut.

​
Where the full set lives

  • Generated endpoint pages (/api-reference/endpoints/*) — the 15-operation split above.
  • Hand-written usage pages (/api-reference/* — messaging, numbers, email, and friends) — every sample group carries the six languages in the fixed order; these pages hold no trimmed pair.
  • Hand-written guides pages (/guides/*) — the same full-set rule: a hand-authored guide carries the six languages on every sample group, regardless of route count (the ≤15-ops trim rule applies to generated endpoint pages, not to guides). The Sandbox API cookbook is the example — its Go/Ruby/PHP tabs spell out each SDK’s escape hatch line (client.Request, client.request, $client->request) for routes below the typed modules.
  • Nav-hint pages — a page that points you to the Worked sequences section for the full group when the headline operation would otherwise trim.
The ordering inside any full group is fixed everywhere: cURL, Node.js (TypeScript), Python, Go, Ruby, PHP.

​
Every endpoint, any language

The Worked sequences section above uses the same fallback the SDK clients do — each SDK exposes an untyped request method that reaches any endpoint with the same authentication, retries, and typed errors:
  • Node.js · Python · Go · Ruby · PHP — the untyped call lives wherever the typed helpers leave off
  • Java · C# — pre-publish, vendor from source
The untyped method is client.request in Java and Ruby, client.RequestAsync in C#, and $client->request in PHP — each language page walks the pattern end to end.