Docs menu

Integrations

Start automations from clicks, QR code scans, new links and email sign-ups, make links from Zapier, Make or n8n, and send sign-ups to Mailchimp or Slack.

siz.la connects to Zapier, Make, n8n, Mailchimp and Slack. The automation tools start from events on your account and can make or change links in return. Mailchimp and Slack are set up in the members area, with no code. Open Integrations there to see what is connected.

Triggers, Slack messages and webhooks are part of the paid plans. Making and changing links from an automation tool works on every plan that can write through the API, and sending sign-ups to Mailchimp works on every plan.

Events a tool can start from

These are the same events the webhooks page describes, so Zapier, Make, n8n and your own code all see the same data.

Event Trigger name Runs when
link.clicked New click Someone clicks one of your links. Bots are left out.
link.created New link A link is made, from the members area, the API or a bulk upload.
bio.signup New email sign-up Someone joins your email list on a bio page.
qr.scanned New QR code scan Someone scans a QR code that points at one of your links.

link.updated and conversion.created are available too, for tools that use webhooks directly.

Clicks and scans are sent together once a minute, so a trigger can run up to a minute after the click.

Zapier

Connect Zapier with your API key. In a Zap, choose siz.la, paste the key when Zapier asks you to sign in, and pick a trigger or an action.

Triggers: New click, New link, New email sign-up and New QR code scan. Each one hands the Zap one item for every click, link or sign-up, with an id, so a Zap never runs twice for the same thing.

Actions: Create a link, Update a link and Find a link. They call the links API, so every option there is available, such as a custom ending, a campaign or an expiry date, as far as your plan allows.

When a Zap that starts from a trigger is turned on, Zapier subscribes to the event with the calls described under Hook subscriptions below, and it removes the subscription when the Zap is turned off. Each subscription shows in the members area, where you can pause or remove it.

Make

Make connects through its custom webhook module for events and its HTTP module for links.

  1. In Make, add a Custom webhook module and copy the address it shows.
  2. Subscribe that address to an event with one request. Replace YOUR_API_KEY and the address.
Shell
curl -X POST https://siz.la/api/hooks \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event": "bio.signup", "target_url": "https://hook.eu1.make.com/your-address", "source": "make"}'
  1. Run the scenario once, then trigger the event. Make learns the fields from the first message it gets. The sample data call under Hook subscriptions shows the shape of every event before one happens.
  2. To make or change links, use the HTTP module with the links API and your API key.

To stop, send DELETE https://siz.la/api/hooks/ID with the id from the subscribe answer, or remove the subscription under Integrations in the members area.

n8n

n8n works the same way as Make, on n8n Cloud and on a server you run yourself.

  1. Add a Webhook node set to POST and copy its production address. The address must start with https:// and be reachable from the public internet, so a workflow that listens on a private machine needs a public address first.
  2. Subscribe it with the call above, using "source": "n8n".
  3. Add an HTTP Request node when you want to make or change links, with the header Authorization: Bearer YOUR_API_KEY.

Check who sent a message

Every message is signed. A tool that wants to check the signature uses the secret from the subscribe answer, which is shown once, and follows the steps on the webhooks page. Zapier does not need it.

If the address answers 410 Gone, siz.la removes the subscription at once. Any other failure is retried and logged like a webhook, and a subscription that fails 25 times in a row is paused.

Hook subscriptions

These calls are what Zapier makes for you, and what you call yourself for Make, n8n or your own tool. They use the same API key as the rest of the API. An account can hold up to 50 subscriptions.

List the events

GET/api/hooks/events

Every event a subscription can ask for, and the trigger name the Zapier app gives it.

Needs: API key.

Example request

Shell
curl "https://siz.la/api/hooks/events" \
  -H "Authorization: Bearer $SIZLA_API_KEY"
JavaScript
const response = await fetch("https://siz.la/api/hooks/events", {
  headers: {
    Authorization: `Bearer ${process.env.SIZLA_API_KEY}`,
  },
});
const data = await response.json();
console.log(data);
Python
import os
import requests

response = requests.get(
    "https://siz.la/api/hooks/events",
    headers={"Authorization": f"Bearer {os.environ['SIZLA_API_KEY']}"},
)
print(response.json())
PHP
$ch = curl_init('https://siz.la/api/hooks/events');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer '.getenv('SIZLA_API_KEY'),
    ],
]);
$data = json_decode(curl_exec($ch), true);

Example answer, status 200

JSON
{
    "error": 0,
    "events": [
        {
            "event": "bio.signup",
            "description": "Someone signs up for email on a bio page",
            "trigger": "New email sign-up"
        }
    ]
}

Notes

  • The real answer lists every event. The trigger is null for an event the Zapier app has no trigger for.

List subscriptions

GET/api/hooks

The subscriptions other tools made with your key. Addresses you added yourself on the Webhooks page are not listed here.

Needs: API key.

Example request

Shell
curl "https://siz.la/api/hooks" \
  -H "Authorization: Bearer $SIZLA_API_KEY"
JavaScript
const response = await fetch("https://siz.la/api/hooks", {
  headers: {
    Authorization: `Bearer ${process.env.SIZLA_API_KEY}`,
  },
});
const data = await response.json();
console.log(data);
Python
import os
import requests

response = requests.get(
    "https://siz.la/api/hooks",
    headers={"Authorization": f"Bearer {os.environ['SIZLA_API_KEY']}"},
)
print(response.json())
PHP
$ch = curl_init('https://siz.la/api/hooks');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer '.getenv('SIZLA_API_KEY'),
    ],
]);
$data = json_decode(curl_exec($ch), true);

Example answer, status 200

JSON
{
    "error": 0,
    "hooks": [
        {
            "id": 14,
            "event": "bio.signup",
            "target_url": "https://hooks.zapier.com/hooks/standard/1/abc",
            "source": "zapier",
            "is_active": true,
            "created_at": "2026-11-14T09:30:00+00:00"
        }
    ]
}

Subscribe to an event

POST/api/hooks

Ask for a message at target_url each time the event happens. The message is the same signed webhook message described on the webhooks page.

Needs: API key with write access. Needs Pro and the plans above it.

Parameters

NameInTypeDescription
event (required)BodystringThe event to subscribe to. One of link.created, link.updated, link.clicked, conversion.created, bio.signup, qr.scanned.
target_url (required)BodystringThe address that receives the messages. It must start with https:// and be on the public internet. Up to 500 characters.
sourceBodystringWhich tool is subscribing. Anything else is saved as api. One of zapier, make, n8n, api.
labelBodystringA name to show next to the subscription in the members area. Up to 120 characters.

Example request

Shell
curl -X POST "https://siz.la/api/hooks" \
  -H "Authorization: Bearer $SIZLA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event":"bio.signup","target_url":"https://hooks.zapier.com/hooks/standard/1/abc","source":"zapier"}'
JavaScript
const response = await fetch("https://siz.la/api/hooks", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.SIZLA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "event": "bio.signup",
    "target_url": "https://hooks.zapier.com/hooks/standard/1/abc",
    "source": "zapier"
  }),
});
const data = await response.json();
console.log(data);
Python
import os
import requests

response = requests.post(
    "https://siz.la/api/hooks",
    headers={"Authorization": f"Bearer {os.environ['SIZLA_API_KEY']}"},
    json={
        "event": "bio.signup",
        "target_url": "https://hooks.zapier.com/hooks/standard/1/abc",
        "source": "zapier",
    },
)
print(response.json())
PHP
$ch = curl_init('https://siz.la/api/hooks');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_CUSTOMREQUEST => 'POST',
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer '.getenv('SIZLA_API_KEY'),
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => json_encode([
        'event' => 'bio.signup',
        'target_url' => 'https://hooks.zapier.com/hooks/standard/1/abc',
        'source' => 'zapier',
    ]),
]);
$data = json_decode(curl_exec($ch), true);

Example answer, status 201

JSON
{
    "error": 0,
    "id": 14,
    "event": "bio.signup",
    "target_url": "https://hooks.zapier.com/hooks/standard/1/abc",
    "source": "zapier",
    "is_active": true,
    "created_at": "2026-11-14T09:30:00+00:00",
    "secret": "whsec_0f1e2d3c4b5a69788796a5b4c3d2e1f001122334"
}

Errors specific to this call

  • 403: The plan does not include webhooks.
  • 422: The event or address is not valid, or the account holds the most subscriptions it can.

Notes

  • secret is shown once, in this answer. Use it to check the signature on each message, or ignore it if the tool does not check.
  • Subscribing the same address to the same event again answers 200 with the subscription that exists and a secret of null.
  • Clicks and scans from now on are sent. Nothing from before the subscription is sent.
  • When the address answers 410 to a message, the subscription is removed.

Remove a subscription

DELETE/api/hooks/{id}

Stop the messages for one subscription.

Needs: API key with write access.

Parameters

NameInTypeDescription
id (required)PathintegerThe subscription id from the subscribe answer.

Example request

Shell
curl -X DELETE "https://siz.la/api/hooks/14" \
  -H "Authorization: Bearer $SIZLA_API_KEY"
JavaScript
const response = await fetch("https://siz.la/api/hooks/14", {
  method: "DELETE",
  headers: {
    Authorization: `Bearer ${process.env.SIZLA_API_KEY}`,
  },
});
const data = await response.json();
console.log(data);
Python
import os
import requests

response = requests.delete(
    "https://siz.la/api/hooks/14",
    headers={"Authorization": f"Bearer {os.environ['SIZLA_API_KEY']}"},
)
print(response.json())
PHP
$ch = curl_init('https://siz.la/api/hooks/14');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_CUSTOMREQUEST => 'DELETE',
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer '.getenv('SIZLA_API_KEY'),
    ],
]);
$data = json_decode(curl_exec($ch), true);

Example answer, status 200

JSON
{
    "error": 0,
    "message": "Hook subscription has been deleted successfully"
}

Errors specific to this call

  • 404: The subscription does not exist, or it is not yours.

Sample data for an event

GET/api/hooks/sample/{event}

A worked example of what an event sends, for a tool that shows sample data while a person sets up a step.

Needs: API key.

Parameters

NameInTypeDescription
event (required)PathstringThe event name. One of link.created, link.updated, link.clicked, conversion.created, bio.signup, qr.scanned.

Example request

Shell
curl "https://siz.la/api/hooks/sample/bio.signup" \
  -H "Authorization: Bearer $SIZLA_API_KEY"
JavaScript
const response = await fetch("https://siz.la/api/hooks/sample/bio.signup", {
  headers: {
    Authorization: `Bearer ${process.env.SIZLA_API_KEY}`,
  },
});
const data = await response.json();
console.log(data);
Python
import os
import requests

response = requests.get(
    "https://siz.la/api/hooks/sample/bio.signup",
    headers={"Authorization": f"Bearer {os.environ['SIZLA_API_KEY']}"},
)
print(response.json())
PHP
$ch = curl_init('https://siz.la/api/hooks/sample/bio.signup');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer '.getenv('SIZLA_API_KEY'),
    ],
]);
$data = json_decode(curl_exec($ch), true);

Example answer, status 200

JSON
{
    "error": 0,
    "event": "bio.signup",
    "items": [
        {
            "id": 77,
            "email": "[email protected]",
            "name": "Sam",
            "page_id": 9,
            "page_name": "Lunch menu",
            "page_url": "https://siz.la/lunch-menu",
            "block_id": "k3d9x2",
            "signed_up_at": "2026-11-14T09:52:10+00:00"
        }
    ],
    "message": {
        "id": "6f1d2c1e-8a47-4c35-9d0b-2a1c0f5e7b90",
        "event": "bio.signup",
        "created_at": "2026-11-14T10:02:44+00:00",
        "data": {
            "signup": {
                "id": 77,
                "email": "[email protected]"
            }
        }
    }
}

Errors specific to this call

  • 404: The event does not exist.

Notes

  • items is what a trigger hands on, one entry for each thing that happened. Each has an id. message is the whole message as it is sent.

Mailchimp

Open Integrations in the members area and choose Connect Mailchimp.

  1. In Mailchimp, open your profile, then Extras, then API keys, and make a key.
  2. Paste the key into siz.la. It is checked with Mailchimp straight away.
  3. Choose the audience that gets your sign-ups. If the account has only one, it is chosen for you.
  4. Pick every bio page, or only some, and choose whether new subscribers confirm by email first.

From then on each new email sign-up on those pages is added to the audience. Someone who unsubscribed in Mailchimp stays unsubscribed. A name entered on the form goes into the first name field.

The key is stored encrypted and is never shown again. Choose Disconnect to delete it.

Sign-ups are sent in the background, and a busy Mailchimp is tried again several times. A sign-up that still fails, for example one Mailchimp keeps on a do-not-contact list, is listed on the Integrations page with the reason Mailchimp gave. Fix the cause, then choose Try failed ones again. Send existing sign-ups adds the ones you collected before you connected.

Slack

  1. In Slack, make an incoming webhook for the channel you want. Slack gives you an address that starts with https://hooks.slack.com/services/.
  2. In siz.la, open Integrations, paste the address under Slack and tick the events you want. You can connect up to 3 channels.
  3. A test message is sent when you add the channel, and Send test sends another.

Slack messages are short sentences, for example a new link, the number of clicks in the last minute by link, or a new sign-up. Treat the address like a password. It is not shown again after you add it, and if Slack stops accepting it the channel is paused and the page says so.