---
title: "Code samples and SDKs"
url: "/help/buuk/code-samples-and-sdks"
updated: "2026-11-13T13:32:05.776Z"
---
# Code samples and SDKs

Every HTTP operation page carries an **Example request** panel of language tabs. Pick a language, copy the snippet, and it runs as written against your base URL.

## Five language tabs

Each operation generates the same request in five flavors:

| Tab | Language |
| --- | --- |
| cURL | a shell command with the full URL, headers, and body |
| Python | a request in that language's standard HTTP stack |
| JavaScript | a fetch-style example |
| Go | a net/http example |
| TypeScript SDK | a call on the generated SDK client (below) |

The samples are reactive: they use the reader's active environment as the base URL, so switching from Production to Sandbox rewrites every tab. The copy button in the panel header copies the active tab, and arrow keys move between tabs.

## Generate a TypeScript SDK

Each spec row in **Help Centre → API Reference** has a download action that produces a single `.ts` file: a typed client generated from your spec. Do not edit it by hand — regenerate it after every sync.

- The full set of request and response types from your spec
- A client class configured with a base URL, default headers, and your own fetch implementation
- An error class that carries the HTTP status of failed calls

Import the file, construct the client once with your base URL and auth header, and every operation is a typed function call. The export is a file, not an npm package — distribution stays in your hands.

> [!TIP]
> Keep the generated file next to the code that calls your API, and re-download whenever the spec diffs forward. A stale SDK and a stale docs page are the same problem with the same fix.

## Postman collection

The second download action produces a Postman collection from the whole spec — every operation, saved as `{spec-name}-postman.json`. Import it into Postman and your QA or partner engineers work from the same source the reference does.

## Related

- Live testing instead of copying: [The Try It playground](./try-it-playground).
- Where the snippets come from: [Import an OpenAPI spec](./import-openapi).
- Token setup for real calls: [API tokens and MCP](./api-tokens-and-mcp).
- What else renders from a spec: [Other reference types](./other-reference-types).