Webhooks and MCP

Webhooks: signed events when something happens

Add an https endpoint with POST /v1/webhooks and pick the events you want, such as post.published, post.failed, post.unknown, post.missed, post.approved, account.reconnect_needed and allowance.low. Each delivery is signed with the Standard Webhooks scheme, using a whsec_ secret that is shown once, so your code can check that it really came from 1Post.

Also:Failures 1Post API reference API authentication and keys

Updated 2026-10-26

Set up

01
Add the endpoint. The address must be public and use https. Scope it to some accounts if you like.
02
Store the whsec_ secret from the reply; it is shown only once.
03
Verify the signature headers on every delivery before you trust the body.
04
Send a test event with POST /v1/webhooks/{id}/test.

Events

post.published, post.failed, post.unknown, post.missed: what happened to a destination.
post.approved: a post was approved.
account.reconnect_needed: an account needs signing in again.
allowance.low: a monthly allowance is nearly used.

A plan allows a set number of endpoints: Starter 5, Creator 25, Agency 100.

Try it