Examples and troubleshooting
Copy-paste calls and error codes explained.
Examples
Schedule a post for tomorrow 6pm:
bash
curl -X POST https://www.mysocials.in/api/public/v1/posts \
-H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
-d '{
"content": "Shipping something new tomorrow.",
"account_ids": ["<account-id>"],
"scheduled_at": "2026-11-08T18:00:00Z"
}'Upload a video and schedule it as a YouTube Short:
bash
curl -X POST https://www.mysocials.in/api/public/v1/media \
-H "Authorization: Bearer $KEY" -F "[email protected];type=video/mp4"
# -> {"url": "/uploads/3f2a....mp4", ...}
curl -X POST https://www.mysocials.in/api/public/v1/posts \
-H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
-d '{
"content": "Why reusing one password is risky.",
"account_ids": ["<youtube-account-id>"],
"media_urls": ["/uploads/3f2a....mp4"],
"type": "short_reel",
"youtube_title": "Password reuse in 60 seconds",
"youtube_made_for_kids": false,
"scheduled_at": "2026-11-08T18:00:00Z"
}'Health-check your integration:
bash
curl -H "Authorization: Bearer $KEY" https://www.mysocials.in/api/public/v1/healthzTroubleshooting
- 401 Unauthorized — key missing, revoked, or malformed. Check the key on the API Keys page; last-used timestamps confirm whether a key is alive.
- 403 Forbidden — the key's scopes don't cover the endpoint. Create a key with the right scope.
- 404 Not Found — the public API isn't enabled for your deployment, or the path is wrong (all paths live under
/api/public/v1). - 413 — media exceeds the upload limit; see Media uploads.