Skip to main content

API reference

Connect Jobby.dev to Zapier and Make

Use webhooks + the Jobby.dev REST API as a custom integration in Zapier / Make to wire Jobby.dev into hundreds of other apps.

Last updated

Jobby.dev doesn't have a first-party Zapier or Make app yet, but the v1 API + webhooks plug into both as a custom integration. ~15 minutes; no code if you stick to the platforms' built-ins.

Zapier — Webhook trigger

Subscribe to Jobby.dev webhooks; route them into a Catch Hook trigger on Zapier. Steps:

  1. In Zapier, create a new Zap with Webhooks by Zapier as the trigger.
  2. Pick Catch Hook, and copy the unique URL Zapier gives you.
  3. Subscribe Jobby.dev to that URL:
    curl https://jobby.dev/api/v1/webhooks \
  -H "Authorization: Bearer $JOBBYDEV_API_TOKEN" \
  -d '{
    "target_url": "https://hooks.zapier.com/hooks/catch/abc/def/",
    "events": ["match.matched", "interview.completed"]
  }'
  4. Fire a test event with POST /api/v1/webhooks/{id}/test so Zapier sees a sample payload.
  5. Add downstream actions in Zapier — Slack, Sheets, Airtable, whatever.

Limitation: Zapier's catch-hook doesn't verify the Jobbydev-Signature. For production use cases where forgery would be costly, sit your own minimal verification proxy in front and forward verified deliveries to the Zapier hook.

Zapier — Action via webhook

For the other direction (something happens elsewhere → call Jobby.dev), use Zapier's Webhooks by Zapier action. Configure:

  • Method: POST (or whatever the endpoint needs).
  • URL: https://jobby.dev/api/v1/....
  • Headers: Authorization: Bearer jbb_....
  • Body: JSON-encoded request body.

Make — HTTP trigger

Make's pattern is similar. Use the Webhook trigger module:

  1. Create a custom webhook; copy the URL.
  2. Subscribe Jobby.dev to that URL with the events you care about.
  3. Fire a test delivery so Make can introspect the payload shape.
  4. Wire downstream modules.

Make — HTTP action

Use the HTTPmodule for outbound calls. Same fields as Zapier's Webhooks action.

Common patterns

  • New match → row in Sheets. Catch-hook on match.matched, then Sheets "Create Spreadsheet Row".
  • New match → email. Catch-hook on match.matched, then Email by Zapier or Gmail. Useful when your team wants a per-match digest.
  • Calendly slot → Jobby.dev event. Calendly trigger → Webhooks action calling POST /api/v1/live-events to create a Jobby.dev event window matching the Calendly slot.
  • Notion page → role. Notion database trigger → Webhooks action calling POST /api/v1/jobs to mirror a role from Notion.

Rate limits

Zapier and Make can fire many actions per minute on a busy account. The 30/minute write rate-limit on Jobby.dev applies to your token, not the platform — back-off shapes the same way as direct API use. See rate limits.

First-party app status

First-party Zapier and Make apps are on the post-Tier 7 backlog. Once shipped, they'll auto-discover events, surface trigger + action templates, and handle signature verification on the Zapier / Make side. Until then, the catch-hook + HTTP-action pattern above works without compromise.

Related reading