Skip to main content
gives you four ways to work with your account. Choose the one that matches the job you need to do.

​
Pick the right starting point

Choose the REST API when your application uses a language other than JavaScript or TypeScript. The API is available through standard HTTPS requests. Use the REST client recipes to start in JavaScript, TypeScript, Python, Go, Java, C#, Ruby, or PHP. Choose the SDK when your JavaScript or TypeScript application needs typed methods and local cryptographic workflows. Choose the CLI when you want a terminal command, a repeatable script, or a way to pass record values to one process without creating a .env file. Choose MCP when you want an AI client to discover and use tools. MCP runs on your machine or in infrastructure you control. Your AI client starts it as a local process. Choose its client guide from the MCP setup page.

​
Identity applies everywhere

Use a human personal access token when you are working as yourself. Use a Service Account when an application or automation needs only the access assigned to that account. The available operations depend on that identity and its permissions. The feature availability reference lists the exact operations available to each identity. Do not work around an access denial by switching to a broader identity.

​
Verify before you write

Start with an operation that only reads status or metadata. Confirm the selected account and project before you create, change, rotate, or revoke anything. This avoids applying a valid command to the wrong place. For workflows that combine more than one integration, see Combine tools.