Developers

API for release marketing operations.

Use the S2P API to inspect workspace state, coordinate approvals, and connect release marketing data to your internal systems.

Scoped keysWorkspace dataVersioned APIStructured errors

At a glance

Workspace-scoped bearer keys.

Every API key belongs to one workspace and can be scoped to the actions your integration needs.

Authentication

Workspace-scoped bearer keys.

Every API key belongs to one workspace and can be scoped to the actions your integration needs.

Header

Authorization: Bearer s2p_<token>

Resources

Current v1 resources.

01

Workspace and members

Read and update workspace metadata, invite members, change roles, revoke access, and list audit logs.

02

Repositories and GitHub connection

List connected repositories, start a GitHub connection, and manage repository access for the workspace.

03

Publishing destinations

List connected destinations, begin OAuth flows, connect Bluesky, refresh credentials, or disconnect channels.

04

Drafts, variants, and posts

List, approve, reject, regenerate, bulk approve, publish, edit variants, and inspect published posts.

05

Brand profiles and templates

Create and manage brand profiles plus channel templates that shape generated post variants.

06

Rules and reporting

Create, update, toggle, and delete trigger rules; query performance metrics for posts and channels.

Response shape

Structured responses for production integrations.

Collection and error shapes

{ "data": { "items": [] }, "meta": { "has_more": false, "next_cursor": null } }
{ "error": "Human readable message.", "code": "machine_readable_code" }

Versioning

Versioned without surprise breakage.

The /v1/ prefix is stable. Additive changes can land in v1; breaking behavior moves to a future /v2/ surface.

Stop writing release posts.

Your engineers already commit. Now those commits become content - in your voice, on every channel.