Introduction

Automate social media publishing with the Maeve Social API

The Maeve Social API lets you programmatically manage workspaces, integrations, content, media, analytics, inbox workflows, and client review operations.

What you can do

  • Create and schedule content: Create drafts, schedule content, publish immediately, update metadata, and retry failed content.
  • Upload media: Create upload sessions, upload files to presigned URLs, then attach media to content with contentMedia.
  • Manage integrations: List connected social accounts, inspect publishing capabilities, and fetch safe dynamic provider options.
  • Use Maeve API keys: Authenticate server-to-server automation with workspace-granted API keys.

Base URL

All public API requests go to:

https://api.maevesocial.com/v1

Workspace-scoped resources use the workspace ID in the path:

/v1/workspaces/{workspaceId}/content
/v1/workspaces/{workspaceId}/media
/v1/workspaces/{workspaceId}/integrations

Use GET /v1/workspaces first to discover the workspace IDs your credential can access.

Response format

Successful responses use a consistent envelope:

{
  "data": { "id": "resource-uuid" },
  "meta": null
}

Paginated list responses include pagination details in meta:

{
  "data": [],
  "meta": {
    "limit": 20,
    "offset": 0,
    "total": 0,
    "hasMore": false
  }
}

Errors on /v1 routes use this shape:

{
  "data": null,
  "error": {
    "code": "NOT_FOUND",
    "message": "Content not found",
    "details": null
  }
}

Error codes

HTTP StatusCodeMeaning
400VALIDATION_ERRORInvalid request body or parameters
401UNAUTHORIZEDMissing or invalid authentication
403FORBIDDENAuthenticated but not allowed
404NOT_FOUNDResource does not exist
409CONFLICTThe request conflicts with current resource state
415UNSUPPORTED_MEDIA_TYPEThe request content type is not supported
429RATE_LIMIT_EXCEEDEDToo many requests
500INTERNAL_ERRORSomething went wrong on our end

Rate limits

The default API limit is 200 requests per 60 seconds per client. Some routes have tighter limits. For example, public workspace resources commonly allow 120 requests per minute, media upload and content writes are lower, and immediate publish/retry routes are lower again.

When a limit is exceeded, the API returns 429 and may include a Retry-After header.

Interactive reference

For the generated OpenAPI reference with every route, request schema, and response schema, visit api.maevesocial.com/docs.