# Build with Playbooks

Use the customer API when your own backend or automation needs to create, inspect, or operate supported Playbooks resources. The same resource roles and Workspace scope that protect work in the app apply to API calls. Keep developer credentials in trusted server-side code.

## Start with a key and Workspace

Create a developer key in Account settings, save its secret, and send it as a Bearer token. For Workspace operations, select an authorized Workspace and include its UUID as the `Workspace` header. Keys may be restricted by permission, Workspace, or Project, and current user and resource access still matters. [Authentication](/docs/reference/authentication) gives the request pattern.

## Choose an interface

Choose the interface that fits where your work runs. The API contract remains the source for supported operations and permissions.

- [**API** Use HTTP requests and inspect endpoint contracts.](/docs/reference/overview)
- [**CLI** Inspect and operate resources from a terminal.](/docs/cli/overview)
- [**MCP** Give an external assistant access to supported Playbooks tools.](/docs/mcp/overview)
- [**SDKs** Use TypeScript or Python in trusted backend code.](/docs/sdks/overview)

Project applications own their own visitor sessions, business permissions, routes, and logic. Playbooks sign-in can establish identity but does not grant application data access. [Projects](/docs/projects/overview) covers development; [Sites](/docs/sites/overview) covers production destinations.

## Example: inspect Projects from a backend

For a server-side process that lists Projects, choose an authorized developer key and Workspace, then start with a read request. Use the SDK for application code, CLI for a terminal workflow, or MCP when an external agent client should invoke the supported tools.

Verify resource selection and error handling before adding mutations. [Authentication](/docs/reference/authentication), [Pagination](/docs/reference/pagination), and [Errors](/docs/reference/errors) establish the common request behavior.