Developer resources

Connect an agent to SlideDrift.

SlideDrift exposes an OAuth-protected JSON API and MCP server for planning, creating, editing, exporting, sharing, and scheduling LinkedIn carousels. Both use the same operations and safety checks. Private browser APIs are not part of the developer contract.

Read the API guide Open the API contract

Predictable machine entry points.

JSON API v1

https://slidedrift.com/api/v1

The versioned JSON API exposes the same typed operations as MCP, with the same OAuth permissions, confirmations, credits, jobs, and rate limits.

Open resource

API v1 OpenAPI contract

https://slidedrift.com/api/v1/openapi.json

A complete OpenAPI 3.1 contract with one HTTP endpoint and input/output schema for every available SlideDrift operation.

Open resource

MCP Streamable HTTP endpoint

https://slidedrift.com/mcp

Connect with an MCP client and complete the browser-based OAuth flow before calling the same operations exposed by API v1.

Open resource

MCP server manifest

https://slidedrift.com/server.json

The schema-valid server.json document identifies SlideDrift by name, implementation version, and remote Streamable HTTP endpoint.

Open resource

Combined discovery contract

https://slidedrift.com/openapi.json

Maps the public API, MCP transport, authorization metadata, permission vocabulary, and typed error shapes from one discovery document.

Open resource

OAuth protected-resource metadata

https://slidedrift.com/.well-known/oauth-protected-resource

RFC 9728 metadata for the MCP resource, authorization server, and SlideDrift permissions enforced by the resource server.

Open resource

Machine-readable product guide

https://slidedrift.com/llms.txt

A concise map of public product documentation, workflows, supported capabilities, and current user-facing product facts.

Open resource

Permission model

SlideDrift binds each OAuth token to the shared agent resource and an enabled account connection. The API and MCP server validate issuer, audience, expiry, ownership, and permission before an operation runs. The consent screen groups permissions by task, so each connection receives only the bundles you select.

carousels:read: Read owned carousels, templates, jobs, credits, campaigns, and schedule state.
carousels:write: Create and edit owned carousels and campaign drafts, and import brand kits from websites, after required confirmations.
covers:read: Search the published cover library and read generated covers owned by the connected account.
covers:write: Generate private covers from library designs or owned images after an exact quote and confirmation.
brand_kits:read: Read brand kits owned by the connected SlideDrift account.
exports:create: Create paid PDF, PNG or image-link exports after an exact quote and confirmation.
shares:write: Create or disable public carousel share links after confirmation.
social:write: Create, update, schedule, or cancel LinkedIn posts after the relevant confirmation.

Errors and recovery

Unknown public API routes return JSON problem details with a stable code, readable detail, and resolution hint. API v1 uses HTTP status codes and problem details; MCP uses JSON-RPC or OAuth bearer errors. Both return safe action URLs, retry guidance, quoted credits, and confirmation metadata when needed.

{
  "status": 404,
  "code": "API_ROUTE_NOT_FOUND",
  "detail": "This URL is not supported.",
  "resolution": "Read /api/v1/openapi.json."
}

Use API v1 for conventional JSON requests or MCP for compatible assistants. Both use browser-based OAuth for connection and authorization. Use the web app for interactive creation and review.

Compatibility and deprecation

SlideDrift negotiates the MCP protocol version during initialize and honors MCP-Protocol-Version on subsequent HTTP requests. Additive tools and optional fields may be introduced within the current implementation version. Breaking tool, authentication, or transport changes require a new implementation version and a documented migration path.

SlideDrift gives at least 90 days of public notice before removing a supported agent operation or required field. During that period, affected HTTP operations are documented as deprecated and return Deprecation and Sunset headers where the transport can represent them. Security, legal, or active-abuse issues may require a shorter emergency window.

Read the versioning and deprecation policy

Tool rate limits

Limits apply across API and MCP to the connected account and, where shown, to each connection. Carousel generation limits depend on the plan, and a trial gets the limits of the plan being trialled. A quota error returns a structuredretryAfterSecondsvalue so the agent can wait and retry safely.

Read tools: 60 per account and 30 per connection, per minute.
Planning tools: 20 per account and 10 per connection, per minute.
Upload tools: 80 per account and 60 per connection, per minute.
Carousel generation and Brand Kit imports: Per account: Free 5 per hour, Starter 5 per 10 minutes, Pro 10 per 10 minutes, Agency 20 per 10 minutes.
Cover generation: 5 per account, per 10 minutes.
Campaign tools: 5 per account and 3 per connection, per hour.
Editing tools: 30 per account and 15 per connection, per hour.
Export, sharing, and scheduling tools: 20 per account and 10 per connection, per hour.
Feature suggestions: 5 per account and 3 per connection, per hour.