set up webhook notifications for your launches
configure webhook endpoints to receive real-time notifications when launches are published, media is generated, and more.
steps
navigate to developer settings
go to your dropspace settings and find the developer section. you'll need an API key — create one if you haven't already.
create a webhook endpoint
add a new webhook by providing your endpoint URL. this should be a publicly accessible HTTPS URL that can receive POST requests.
for local development, use a tunneling service like ngrok to expose your local server to the internet.
configure event types
select which events you want to receive: launch.published, launch.completed, launch.failed, media.completed, persona.completed, and more. start with just the events you need.
test with a sample event
use the test button to send a sample payload to your endpoint. verify that your server receives and acknowledges the request with a 200 status code.
handle webhook payloads in your app
parse the incoming JSON payload in your application. each event type has a specific payload structure documented in the API reference.
verify webhook signatures
validate the X-Webhook-Signature header using HMAC-SHA256 with your webhook secret. this ensures the request genuinely came from dropspace.
always use timing-safe comparison when verifying signatures to prevent timing attacks.
security best practices
- always verify signatures — never process a webhook without validating the HMAC signature. this prevents spoofed requests.
- use HTTPS — webhook endpoints should always use HTTPS to encrypt payloads in transit.
- respond quickly — return a 200 status code within 5 seconds. do heavy processing asynchronously after acknowledging receipt.
- handle duplicates — implement idempotency using the event ID. webhooks may be retried, so your handler should be safe to call multiple times.
retry behavior
if your endpoint returns a non-2xx status code or times out, dropspace will retry the webhook delivery with exponential backoff. retries happen at approximately 1 minute, 5 minutes, and 30 minutes after the initial attempt. after 3 failed retries, the event is marked as failed and can be viewed in your developer dashboard.
ready to launch?
join thousands of makers who use dropspace to launch across 9+ platforms with AI-generated content.