If it can make an HTTP request, it can publish through SchedPilot. One endpoint, one key, every network you have connected — and no per-platform integrations to maintain.
In SchedPilot, open API Access and generate a key. It starts with smm_.
Point it at the developer API with your key as a bearer token.
Posts land in your calendar for approval, exactly as they would from the app.
curl -X POST https://api.schedpilot.com/developers/v1/post \
-H "Authorization: Bearer smm_your_key" \
-H "Content-Type: application/json" \
-d '{"content":"Shipping today","date":"2026-07-10","time":"09:00",
"accounts":[{"id":12,"type":"linkedin"}]}'
Replace smm_your_key with the key from API Access in your SchedPilot account.
Rate limits are 150 read and 100 write requests per hour, per user. Scheduling a post with media costs two writes.
Nine networks means nine OAuth flows, nine token refresh schedules and nine sets of posting quirks. That is weeks of work and a permanent maintenance cost. This is one endpoint instead.
Things that work well once Your own agent is connected.
Full reference, including every field and error code, is in the developer docs.
There is a setup guide for every agent we support, plus a REST API for anything that is not on the list.
See all agentsFree to start, and every post waits for your approval.
Start for freeSchedule posts, find your best time to publish, and keep your calendar full — without the chaos. SchedPilot makes consistency simple across every channel.
Start for freeFree trial available. Cancel anytime.