create your first dropspace API integration
build a complete integration with the dropspace API — from authentication to creating launches, generating content, and monitoring via webhooks.
steps
create an API key with appropriate scopes
navigate to developer settings and create a new API key. select the scopes you need: launches:read, launches:write, personas:read, media:read, and webhooks:manage.
follow the principle of least privilege — only request the scopes your integration actually needs.
install the SDK or set up HTTP client
install the @jclvsh/dropspace-mcp package for a type-safe client, or use any HTTP client to call the REST API directly at api.dropspace.dev.
authenticate requests
include your API key in the Authorization header as a Bearer token: Authorization: Bearer ds_live_... — all API requests require this header.
create a launch via API
make a POST request to /v1/launches with your launch name, description, and target platforms. the API returns the created launch with its ID for subsequent operations.
generate content for the launch
call POST /v1/launches/{id}/generate-content to trigger AI content generation. optionally specify a persona ID to use your brand voice. content is generated asynchronously.
trigger publishing
when your content is ready, call POST /v1/launches/{id}/publish to start publishing across all configured platforms. the API returns immediately while publishing happens in the background.
monitor via webhooks
set up webhooks (see the webhook guide) to receive launch.published and launch.completed events. this lets your integration react in real-time without polling.
rate limiting
the dropspace API enforces rate limits per API key. standard keys allow 60 requests per minute. if you exceed this limit, the API returns a 429 status code with a Retry-After header indicating when you can resume requests. implement exponential backoff in your integration to handle rate limits gracefully.
error handling
- 4xx errors — client errors like invalid input (400), unauthorized (401), not found (404), or rate limited (429). fix the request before retrying.
- 5xx errors — server errors that are safe to retry with exponential backoff.
- error response format — all errors return a JSON body with { error: { code, message } } for consistent handling.
next steps
- explore the full API documentation for all available endpoints.
- set up webhook notifications for real-time event processing.
- use the MCP package to integrate dropspace into your AI workflows.
ready to launch?
join thousands of makers who use dropspace to launch across 9+ platforms with AI-generated content.