Inbound Webhooks
Send events into Logspot from any system that can POST JSON, without installing an SDK.
An inbound webhook gives each project a URL you can POST an event to. Use it when the system producing the event cannot run a Logspot SDK: a no-code tool, an automation platform such as Zapier or Make, a CI job, or a backend in a language without an SDK.
For the other direction, sending data out of Logspot to your own endpoint, see Receiving Webhooks.
Your Webhook URL
The URL is unique per project and is shown on the project's details page in the dashboard. It looks like this:
https://api.logspot.io/hooks/{projectShortId}/{projectWebhookSecret}The secret is part of the path, so treat the whole URL as credentials. Anyone holding it can write events into your project. If you need to separate sources, create a separate project rather than sharing one URL.
No authentication header is needed, because the URL itself carries the secret.
Sending an Event
curl https://api.logspot.io/hooks/abc123/s3cr3t \
-H "Content-Type: application/json" \
-d '{
"name": "Subscription Started",
"user_id": "jane@example.com",
"metadata": { "plan": "pro", "seats": 12 }
}'Body
| Field | Required | Notes |
|---|---|---|
name | Yes | The event name, for example Subscription Started |
user_id | No | Links the event to a person. An id, a UUID, or an email all work |
metadata | No | Any JSON object. Becomes event properties you can filter and group by |
message | No | A short string, up to 350 characters, shown alongside the event |
notify | No | Accepted for backwards compatibility. Nothing reads it, and it fires no notification |
To send a notification when this event arrives, create a Send Notification action matching the event name. That is the supported route, and it works regardless of how the event was sent.