Webhooks
There are no outbound webhooks
You cannot subscribe to Postlyra events. There is no webhook subscription model, no delivery log, no signing secret to configure, and no endpoint that registers a callback URL.
Nothing notifies you when a post publishes, a DM arrives, or a slot fails.
The webhook endpoints that exist in Postlyra are inbound callbacks from platforms we integrate with. They are part of how connections stay alive, and they are not something you call or subscribe to.
| Endpoint | Who calls it |
|---|---|
POST /webhooks/meta/deauthorize | Meta, when a user removes the app |
POST /webhooks/meta/data-deletion | Meta, on a data deletion request |
GET and POST /webhooks/meta/instagram | Meta, delivering Instagram events such as DMs and comments |
GET /oauth/{platform}/callback | The platform, finishing an OAuth connect |
| Stripe's webhook | Stripe, on billing events |
These live on a separate host and verify signatures from the calling platform. They are documented here only so nobody wires an integration against them by mistake.
Polling instead
Until outbound webhooks exist, poll. Match the interval to how fast the data actually changes.
| What you want | Endpoint | Sensible interval |
|---|---|---|
| New ideas in the queue | list_ideas on MCP | Minutes |
| Whether a plan changed | GET /subscription/status | Hourly |
| Remaining allowances | GET /me/entitlements | Hourly |
Metrics sync once a night, so polling them more often than daily reads the same numbers repeatedly. See Rate limits.
If you need push
Say so. Outbound webhooks are a known gap rather than a deliberate omission, and knowing which events people actually want is what decides the order they get built in.