Webhooks & automation
Add a webhook_url to any job and we POST the result to you the moment it's ready — no polling, no held connections. This is the backbone for n8n, Zapier, and custom pipelines.
The payload
When a job finishes (success or failure), we send a single POST to your webhook_url:
{
"job_id": "385df601-fafb-4549-b8a8-…",
"status": "completed",
"output_url": "https://…/your-video.mp4"
}statusiscompletedorfailed.output_urlis present on success and points to the finished MP4.- On failure there is no
output_url— and remember, failed jobs cost $0. - Stories use the same payload, with
job_idcarrying the story id and one delivery for the stitched video.
Delivery headers
| Header | Meaning |
|---|---|
| X-GetMeCompute-Event | The job status this delivery reports (completed / failed). |
| X-GetMeCompute-Delivery | Stable id for this event (job_id:status). If your endpoint sees the same value twice, it's a redelivery — safe to ignore the duplicate. |
| X-GetMeCompute-Timestamp | Unix timestamp of the delivery attempt. |
| User-Agent | GetMeCompute-Webhook/1 |
Retries
Respond with any 2xx quickly — do heavy work after acknowledging. If your endpoint returns a server error or times out, we retry the delivery; permanent client errors (e.g. 404) are not retried. Because retries can deliver the same event twice, use X-GetMeCompute-Delivery to dedupe.
webhook_url — including jobs submitted from the dashboard form. That means you can build full automations today, even before standalone API keys ship: submit from the dashboard, let the webhook drive the rest.Recipe: n8n
- Add a Webhook trigger node and copy its production URL.
- Paste that URL into the Webhook URL field when submitting your GetMeCompute job.
- In the workflow, branch on
{{ $json.body.status }}—completedvsfailed. - On success, use an HTTP Request node to download
output_url, then continue — upload to your CMS, post to social, notify Slack, or kick off the next job.
Recipe: Zapier
- Create a Zap with Webhooks by Zapier → Catch Hook and copy the custom webhook URL.
- Use it as the Webhook URL on your GetMeCompute job.
- Add a Filter step for
status = completed, then any action you like — save the video to Drive/Dropbox fromoutput_url, add a row to a sheet, send an email.
Recipe: your own backend
Expose an HTTPS endpoint, store the payload, and return 200 immediately. Download the video from output_url in a background task. Track job_id against the id returned when you submitted the job to correlate results.