Subscribe to a Netlify event
Subscribe to a Netlify event. castomAPI registers the webhook against its own signed receiver and stores what arrives, readable at GET /v1/netlify/webhooks/events
Request
- x-api-key: <your-api-key>
- Content-Type: application/json
Response
{
"hook": {
"createdAt": "2026-09-08T10:00:00Z",
"disabled": true,
"event": "<event>",
"id": "crd_600089",
"siteId": "sit_193467",
"success": true,
"type": "standard",
"updatedAt": "2026-09-08T10:05:00Z"
},
"status": "success",
"tokensDeducted": 1
}What it does
Subscribe to a Netlify event. castomAPI registers the webhook against its own signed receiver and stores what arrives, readable at GET /v1/netlify/webhooks/events
Request
Body
| Field | Type | Required | Description |
|---|---|---|---|
accountId | string | no | Which connected Netlify account to use, when more than one is connected |
event | enum | yes | The event to subscribe to. One hook carries exactly one event. One of: submission_created, split_test_activated, split_test_deactivated, split_test_modified, deploy_request_pending, deploy_request_accepted, deploy_request_rejected, deploy_restored…. |
site_id | string | yes | The site UUID |
Example request
{
"accountId": "acc_600841",
"event": "submission_created",
"site_id": "sit_594760"
}Response
| Field | Type | Description |
|---|---|---|
hook | object | |
↳ createdAt | string | |
↳ disabled | boolean | |
↳ event | string | |
↳ id | string | |
↳ siteId | string | |
↳ success | boolean | |
↳ type | string | |
↳ updatedAt | string | |
status | string | |
tokensDeducted | integer |
Example response
{
"hook": {
"createdAt": "2026-09-08T10:00:00Z",
"disabled": true,
"event": "<event>",
"id": "crd_600089",
"siteId": "sit_193467",
"success": true,
"type": "standard",
"updatedAt": "2026-09-08T10:05:00Z"
},
"status": "success",
"tokensDeducted": 1
}Errors
Every error answers with the same envelope: an HTTP status, a machine code and a sentence.
400 | The body or a parameter failed validation. The details array names the field. |
401 | No key, a revoked key or a wrong header. Send x-api-key. |
402 | The wallet cannot cover this call. Top up or wait for the monthly grant. |
404 | The resource does not exist, or it is not yours. Both answer identically and cost nothing. |
429 | Over the per-minute quota of your tier. Back off and retry. |
5xx | Upstream refused or timed out. The call is not billed. |
Code
curl -X POST 'https://app.castomapi.com/v1/netlify/hooks' \
-H 'x-api-key: <your-api-key>' \
-H 'Content-Type: application/json' \
-d '{"accountId": "acc_600841", "event": "submission_created", "site_id": "sit_594760"}'const res = await fetch('https://app.castomapi.com/v1/netlify/hooks', {
method: 'POST',
headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
body: JSON.stringify({"accountId": "acc_600841", "event": "submission_created", "site_id": "sit_594760"})
});
const data = await res.json();
console.log(data);import { request } from 'node:https';
// Node 18+ has fetch built in
const res = await fetch('https://app.castomapi.com/v1/netlify/hooks', {
method: 'POST',
headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
body: JSON.stringify({"accountId": "acc_600841", "event": "submission_created", "site_id": "sit_594760"})
});
const data = await res.json();
console.log(data);import requests
res = requests.post(
'https://app.castomapi.com/v1/netlify/hooks',
headers={'x-api-key': '<your-api-key>'},
json={"accountId": "acc_600841", "event": "submission_created", "site_id": "sit_594760"},
timeout=30,
)
print(res.json())<?php
$ch = curl_init('https://app.castomapi.com/v1/netlify/hooks');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => ['x-api-key: <your-api-key>', 'Content-Type: application/json'],
CURLOPT_POSTFIELDS => json_encode(['accountId' => 'acc_600841', 'event' => 'submission_created', 'site_id' => 'sit_594760']),
]);
$data = json_decode(curl_exec($ch), true);
print_r($data);Cost and limits
This operation costs 1 token. A call that fails is never billed. Every account gets 1000 free tokens a month; paid balances never expire.
Rate limits per minute
| No key | 10 |
| Free | 60 |
| Pro | 300 |
| Enterprise | 1200 |
Questions
What does Subscribe to a Netlify event cost?
1 token per successful call, debited from your wallet after the response. Failed calls are free. Every account receives 1000 free tokens a month.
How do I authenticate?
Send your key in the x-api-key header. One key covers every metered endpoint; there is nothing to enable per endpoint.
Can I send an Authorization: Bearer token instead?
Not for a metered endpoint — those take the x-api-key header and nothing else. Bearer tokens belong to the account side: the dashboard and account APIs accept a JWT session, and castomapi-auth issues those through a standard OAuth2 handshake, with authorization code, client credentials and refresh grants. The auth service page covers it.
What are the limits?
10 requests a minute per IP with no key at all, 60 a minute on the free tier, 300 on Pro, 1200 on Enterprise. Above the no-key tier the quota is per account, across every endpoint.
OpenAPI: https://app.castomapi.com/docs/json