Skip to main content
The Developers section provides tools for technical integrations beyond the built-in ones (Shopify, Instagram). Use API keys and webhooks to connect Fanhaven with your own systems.

​
API keys

API keys allow external applications to authenticate with the Fanhaven API.

​
Creating an API key

2
From the dashboard, go to Settings → Developers.
3
Click “Create API Key”
4
Give the key a descriptive name (e.g., “Warehouse System Integration”) so you can identify it later.
5
Copy and store the key
6
The API key is shown once at creation. Copy it and store it securely — you won’t be able to see the full key again.

​
API key scopes

API keys are scoped to:
  • Artist level — Access to a specific artist’s data
  • Tour level — Access to a specific tour’s data
This ensures that external integrations only access the data they need.

​
Revoking a key

If a key is compromised or no longer needed:
  1. Go to the Developers page
  2. Find the key in the list
  3. Click Revoke
  4. The key is immediately invalidated
Revoked keys cannot be restored. Any system using the revoked key will immediately lose access. Make sure to update external systems with a new key before revoking the old one.

​
Webhooks

Webhooks send real-time notifications to external URLs when events happen in Fanhaven.

​
Setting up a webhook

1
Go to Developers
2
Navigate to the Developers section.
3
Click “Add Webhook Endpoint”
4
Enter the URL where you want to receive webhook events.
5
Select events
6
Choose which events trigger notifications:
7
EventDescriptionTransaction createdA sale is completedTransaction refundedA refund is processedFan createdA new fan signs upInventory updatedStock levels changeOrder status changedA mobile/online order status changes
8
Save
9
The webhook is active and will start sending events to your endpoint.

​
Webhook security

Each webhook endpoint has a signing secret that you can use to verify that incoming requests are genuinely from Fanhaven:
  1. When the webhook is created, a signing secret is generated
  2. Each webhook request includes a signature header
  3. Your server verifies the signature using the secret
You can roll the secret if it’s compromised — the old secret becomes invalid immediately and a new one is generated.

​
Webhook delivery

  • Webhooks are sent as HTTP POST requests with a JSON payload
  • If your endpoint returns a non-2xx status code, Fanhaven retries the delivery
  • Failed deliveries are logged and visible in the Developers section

​
Use cases

IntegrationHow to build it
Warehouse managementWebhook on inventory changes → update your WMS
Custom analyticsWebhook on transactions → feed into your data warehouse
CRM syncWebhook on fan creation → create a contact in your CRM
NotificationsWebhook on high-value transactions → alert in Slack
For most teams, the built-in integrations (Shopify, Instagram) and dashboard features are sufficient. The Developers section is for teams with custom technical needs or existing systems that need to receive Fanhaven data in real time.