dropspace developer API v1

the dropspace API follows RESTful conventions with a few opinionated choices that prioritize developer experience:

• consistent response shape — every response returns { success, data, error } so you always know what to expect
• typed error codes — machine-readable error codes (like LAUNCH_001) alongside human-readable messages
• scoped permissions — API keys can be restricted to specific operations, following the principle of least privilege
• idempotent operations — safe to retry failed requests without side effects

the API is versioned at /api/v1 and accessible at api.dropspace.dev.

API keys follow the format ds_live_... and are passed via the Authorization: Bearer header. keys are hashed with SHA-256 at rest — we never store the raw key.

each key can be scoped to specific permissions:

• launches:read / launches:write — view and manage launches
• content:write — generate AI content for launches
• media:write — generate and manage media assets
• personas:read / personas:write — view and manage brand personas
• webhooks:read / webhooks:write — manage webhook subscriptions
• publish:write — trigger launch publishing across platforms

keys are created from the settings page in the dropspace dashboard.

the v1 API covers the core dropspace workflow:

see the full endpoint reference in the developer docs.

webhooks notify your application when events happen in dropspace. configure endpoints from the dashboard or via the API, and we'll send POST requests with event payloads.

supported events:

• launch.published — a launch was published to platforms
• launch.completed — all platform posts finished (success or failure)
• content.generated — AI content generation completed
• media.completed — media generation (image or video) finished
• persona.analyzed — persona AI analysis completed

all webhook deliveries include an HMAC signature in the X-Dropspace-Signature header for verification. deliveries are retried up to 3 times with exponential backoff on failure.

API requests are rate limited per key to ensure fair usage. when you hit a limit, the API returns HTTP 429 with a Retry-After header indicating when you can retry.

current limits:

• general endpoints — 60 requests per minute
• content generation — 10 requests per minute (Claude API cost)
• media generation — 5 requests per minute (GPU compute cost)
• publishing — 5 requests per minute (platform rate limits)

rate limit headers are included in every response: X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset.

to start using the API:

1. create an API key from the settings page with the scopes you need
2. make your first request to GET api.dropspace.dev/launches
3. explore the full reference in the developer docs

machine-readable documentation is also available at /llms.txt and /openapi.json for AI agents and code generation tools.