Create a playbook
ai-sdr:write scope (or a broader one that includes it).
Use this endpoint when you need a new playbook to hold the tone, voice and writing guidance your AI SDR should follow. All four fields are required: name of up to 128 characters, description of up to 1000 characters, body carrying the guidance itself, and type — either organization to share the playbook across your organization or team to keep it to your own team, since global playbooks are Reply-curated and cannot be created here. The description and body fields accept an empty string if you would rather fill them in later, and any template variables used in body must be ones your account recognizes; creating an organization playbook also needs your account to be allowed to create organization playbooks. The created playbook is returned in full with its assigned id, which carries the o- or t- scope prefix. The AI SDR feature must be enabled for your team.
Authorizations
Authenticate every request with a Bearer token. Pass your Reply API key in the
Authorization header:
Get your API key from the Reply dashboard: Settings → API Key.
Body
Request body for creating a new playbook.
Display name of the playbook
1 - 128Short description of the playbook's purpose. Empty string allowed.
1000Full playbook body — typically Markdown or plain text instructions the AI SDR follows when this playbook is applied. Empty string allowed.
Visibility scope for the new playbook. Only organization and team are accepted —
global playbooks are Reply-curated and cannot be created via the API.
global, organization, team Response
Playbook created successfully
Detailed representation of a playbook, returned by get/create/update responses.
Composite identifier formatted as {prefix}-{numericId} where the prefix encodes the playbook scope:
g for global, o for organization, t for team (e.g. g-1, o-42, t-7).
Display name of the playbook
Short description of the playbook's purpose
Full playbook body — typically Markdown or plain text instructions the AI SDR follows when this playbook is applied.
Visibility scope of the playbook. Set on create and immutable thereafter.
global, organization, team Timestamp of the last modification
User ID of the playbook author. null for global playbooks and when the original author is no longer a team member.
Style files attached to the playbook. Managed via the /style-files sub-resource — uploads are immediate, deletes are immediate; the field is read-only on the playbook payload.