API & Webhooks

Go to Settings → Integrations to create API keys. API keys let you build custom integrations or automate tasks with the FillCue API.

Each key can have Read and/or Write scope. Keys are shown only once when created — copy it immediately.

Availability: Individual and Coordinator plans.

The FillCue REST API is available at /api/v1/. Authenticate every request with a Bearer token:

Authorization: Bearer fc_live_your_key_here

Available endpoints:

Method	Endpoint	Scope	Description
GET	/api/v1/contacts	read	List all contacts
POST	/api/v1/contacts	write	Create or update a contact
GET	/api/v1/gigs	read	List all events
POST	/api/v1/gigs	write	Create an event
GET	/api/v1/cascades/:id	read	Get outreach details
POST	/api/v1/cascades/:id/pause	write	Pause outreach
POST	/api/v1/cascades/:id/resume	write	Resume outreach
POST	/api/v1/cascades/:id/cancel	write	Cancel outreach

All responses are JSON. Errors return { "error": "message" } with appropriate HTTP status codes (400, 401, 404, 429).

Webhooks send real-time event notifications to a URL you specify. For example, get notified instantly when someone accepts an outreach.

Events you can subscribe to:

• Outreach: started, completed, exhausted, cancelled, paused, resumed
• Offers: pending, accepted, declined, expired
• Gigs: created, updated, deleted
• Contacts: created, updated, deleted

Availability: Individual (2 endpoints) and Coordinator (10 endpoints) plans.

Every webhook delivery includes an X-FillCue-Signature header containing an HMAC-SHA256 signature of the request body. Verify this signature against your webhook’s signing secret to ensure the request is genuine.

Your signing secret is shown once when the webhook is created. You can rotate it from Settings → Integrations at any time (the old secret stops working immediately).

Webhooks that fail delivery 10 consecutive times are automatically disabled. You can re-enable them from the integrations page.