The Optimate API

1. In Optimate, open Settings → Automations and find API keys.
2. Name the key after what will use it, like “Zapier”, so you know which to revoke later.
3. Choose Read and post to schedule and publish, or Read only for reports and dashboards.
4. Copy the key straight away. It starts with opt_live_ and is shown only once.

Send the key in the Authorization header on every request. Everything is JSON. Start by checking the key works:

curl https://www.optimatesocial.com/api/v1/me \
  -H "Authorization: Bearer opt_live_YOUR_KEY"

Then see which accounts you can post to. Each one has an accountId you can use to pick it:

curl https://www.optimatesocial.com/api/v1/accounts \
  -H "Authorization: Bearer opt_live_YOUR_KEY"

If you manage several clients, the API works on whichever client is active in Optimate, exactly like the app. Switch client in Optimate to reach another client's accounts.

Give a caption, the platforms and a time. Times are your local time with no offset, read in the timezone your Optimate account uses (/accounts tells you which).

curl https://www.optimatesocial.com/api/v1/posts \
  -H "Authorization: Bearer opt_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "caption": "Our autumn menu starts Monday",
    "platforms": ["instagram", "facebook"],
    "scheduledFor": "2026-10-20T09:00",
    "mediaUrl": "https://…"
  }'

Instagram and Pinterest need a picture, and TikTok and YouTube need a video. A mediaUrl must be a file already in Optimate: one from GET /media, POST /designs or POST /images.

Check before you send. Add "preview": true to see exactly what would happen, without scheduling anything. The answer includes a confirmToken. Send the same request again with that confirmToken (and without preview) to go ahead.

Retrying is safe with a token. If a request with a confirmToken times out, send it again with the same token: Optimate reports what already happened instead of posting twice. A request without a token also returns the token it used, so keep it.

POST /posts/publish works the same way but posts straight away, and can't be undone. Client approval still applies: a scheduled post for a client who approves posts waits for their approval, and such a client can't be published to straight away.

There is no Optimate app inside Zapier or Make yet, but both can call the API directly, so you can connect Optimate today.

• Zapier: add a Webhooks by Zapier action, choose Custom Request, set the method to POST, the URL to https://www.optimatesocial.com/api/v1/posts, add a header Authorization with the value Bearer opt_live_YOUR_KEY, and put the JSON from step 3 in the data box.
• Make: add an HTTP → Make a request module with the same URL, method, header and JSON body.

For a Zap that runs on its own, consider POST /drafts instead: the post waits in your Planner for you to check and schedule.

All paths start with https://www.optimatesocial.com/api/v1. The full reference, with every field, is the OpenAPI document, which tools like Postman can import.

When something is refused, the answer has an HTTP error status and a sentence you can show a person:

{ "error": { "message": "scheduledFor must be at least a minute in the future." } }

• 400: the request is malformed, such as an unknown field.
• 401: the key is missing, wrong or revoked.
• 403: the key is read-only, your team role is view-only, or your plan doesn't include the API.
• 422: Optimate understood the request but couldn't do it, such as a time in the past.
• 429: too many requests. Wait for the number of seconds in the Retry-After header.

Each key can make 60 requests a minute, and each account 120 across all its keys. Of those, 20 a minute may schedule, publish, edit or create. Designs use 1 AI credit and AI images use 10, from the same credits as the app.

• A key works like your password for the API. Keep it on a server or in Zapier, never in a web page or an app people can download.
• Make one key per tool, and give it Read only unless it needs to post.
• We store only a scrambled fingerprint of each key, so nobody at Optimate can read it back.
• Revoke a key in Settings → Automations and it stops working on the very next request. Settings also shows when each key was last used.
• If you're a team member, a key acts with your role in the workspace you're working in. A view-only member's key can only read.

Questions or something missing? Get in touch.