BUILD WITH SEEMOAI · API V1

Your content workflow.
Connected to SeemoAi.

Use the public REST API to read connected accounts, prepare posts, schedule content and submit it to your social platforms.

Create an API key OpenAPI specification

1. Get connected

Sign in to SeemoAi and connect your social accounts through Social Accounts.
Open API & Integrations in your dashboard and create a key. Choose the minimum permissions your workflow needs.
Save the key securely. It is shown only once.

Base URL: https://seemoai.com/api/v1

curl https://seemoai.com/api/v1/accounts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

Keys expire after 30, 90 or 365 days and can be revoked immediately. Do not put API keys in website JavaScript, public repositories or URLs. Use your automation tool’s private credentials storage.

2. Create a draft

Copy an account ID from GET /accounts. Each request creates one post for one connected account. A post credit is consumed on creation, including drafts. Cancellation does not refund it.

curl https://seemoai.com/api/v1/posts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: my-workflow-post-001" \
  -d '{"account_id":123,"text":"A new update from our team."}'

Use a unique Idempotency-Key for each new post. Repeating the same key and body returns the existing post without consuming another credit. Reusing a key with different content returns 409.

3. Add media or schedule

For media, send multipart form data with media[]. Upload up to four JPG/PNG images (up to 24 megapixels each) or one MP4 video, maximum 20 MiB per file. The server’s total upload limit may be lower. Remote media URLs are not accepted in v1.

curl https://seemoai.com/api/v1/posts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json" \
  -H "Idempotency-Key: my-workflow-video-001" \
  -F "account_id=123" \
  -F "title=Our latest update" \
  -F "text=Watch our latest video." \
  -F "media[]=@video.mp4"

For scheduling, include scheduled_at, for example 2027-01-20T15:00:00+00:00. It must be in the future. Times are stored in UTC. Scheduling requires publish permission and a plan with scheduling. Scheduled submissions are checked every minute; exact delivery time depends on server load and the social platform.

Instagram requires media. TikTok and YouTube require exactly one MP4; YouTube also requires a title. Platform-specific size, duration and account restrictions still apply. TikTok currently submits videos with private visibility (SELF_ONLY).

4. Submit a draft

curl -X POST https://seemoai.com/api/v1/posts/456/publish \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

This can publish externally. Use a key with publish permission. Repeated requests for the same post do not submit it again. The response may take time while the social provider processes the request.

Submitted does not guarantee publicly visible. It means SeemoAi’s provider service accepted the submission. Provider processing, permissions and moderation can still affect delivery. Check the destination account.

Endpoints

Method & path	Permission	Purpose
GET /me	Read	Plan and remaining post credits
GET /accounts	Read	Connected accounts; 50 per page
GET /posts	Read	API-created posts; 25 per page
GET /posts/{id}	Read	One API-created post and its submission state
POST /posts	Write; Publish for schedules	Create a draft or scheduled post
POST /posts/{id}/publish	Publish	Submit a draft once
DELETE /posts/{id}	Write	Cancel a draft or schedule; does not delete a social post

Use ?page=2 for lists. Post IDs are SeemoAi IDs, not social network IDs. This API lists and manages posts created through API v1. Social connections are authorized through the dashboard, not through the public API.

States and errors

States: draft, scheduled, publishing, submitted, failed, unknown, cancelled.

A failed or unknown publication is not automatically retried. Check the destination account before creating another post to avoid duplicates. A publishing request interrupted for over 15 minutes becomes unknown.

HTTP codes: 401 missing/expired key; 403 missing permission, inactive account or plan restriction; 404 resource not found; 409 conflicting request/state; 422 invalid input; 429 rate limit. Validation errors include an errors object; other API errors use error.code and error.message.

Limits: 60 API requests per minute per caller/IP under the existing API limiter, plus 10 write requests per minute and 5 publish requests per minute per user. On 429, wait for the Retry-After period. A revoked key stops requests but does not cancel posts already scheduled.

Automation tools

In n8n or Make, use an HTTP request step with the base URL, Bearer authentication, JSON or multipart body, and the Idempotency-Key header for post creation. No custom connector is required.

API v1 uses the existing Facebook, Instagram, LinkedIn, X, TikTok and YouTube services. Availability depends on connected accounts, subscriptions and provider approvals. Comments, DMs, analytics, webhooks, AI generation and a hosted MCP server are not included in this release.

API-created posts can be viewed in the dashboard. Manage and cancel them through the API; dashboard editing is disabled to keep submission state consistent.

Contact SeemoAi support · API v1

API Documentation