Write Post API

Overview

The Write Post API is separate from the SMM Panel API. Shared authentication does not merge their business logic or documentation. One API key may enable write_post, smm, or both.

Permission

Requests require an API key with write_post enabled (write_post_enabled on the key).

Smoke check:

curl -X GET "https://engagegrove.com/api/v1/write-post/ping/" \
  -H "Authorization: Bearer YOUR_API_KEY"

Social connections

Connecting and disconnecting social accounts is managed in the dashboard. The public API can list active connections and use their IDs when creating posts. OAuth secrets are never returned.

Live endpoints

• GET /api/v1/write-post/ping/ — permission check
• GET /api/v1/write-post/connections/
• GET /api/v1/write-post/cost/
• POST /api/v1/write-post/posts/ — create / publish / schedule
• GET /api/v1/write-post/posts/
• GET /api/v1/write-post/posts/{id}/
• POST /api/v1/write-post/bulk/
• POST /api/v1/write-post/bulk/validate/ — dry-run CSV validation (see Bulk Upload)

Coming soon

• Dedicated POST /posts/{id}/publish and POST /posts/{id}/schedule routes — today use Create Post with/without scheduled_at