API Reference

Integrate your tools and workflows with the Creator Studios API. Build custom integrations, automate tasks, and extend your creative pipeline.

Overview

The Creator Studios API provides programmatic access to our platform's tools and documentation. It follows RESTful conventions, returns JSON responses, and is designed to be simple and predictable.

All read endpoints are publicly accessible and require no authentication. Write and admin endpoints will require an API key in a future release. Every response includes standard HTTP status codes to indicate success or failure.

Note: The API is currently in beta. Endpoints and response shapes are stable, but we may add new fields and capabilities. We will announce any breaking changes in the changelog.

Base URL

All API requests should be made to the following base URL:

https://api.creatorstudios.org/v1 (copy)

Append the desired endpoint path to this base URL. For example, a request to list all tools would use https://api.creatorstudios.org/v1/tools.

Endpoints

The following endpoints are available in the current version of the API:

GET /tools List all available tools
GET /tools/:slug Get details for a specific tool
GET /docs/:slug Get documentation content by slug

GET /tools

Returns a list of all tools available in Creator Studios. Each tool object includes its slug, name, description, icon identifier, and category.

Response — 200 OK 
{
  "data": [
    {
      "id": "thumbnail-tester",
      "slug": "thumbnail-tester",
      "name": "Thumbnail Preview Tester",
      "description": "Preview and compare YouTube thumbnail variations in real time.",
      "category": "thumbnails",
      "icon": "image"
    },
    {
      "id": "title-analyzer",
      "slug": "title-analyzer",
      "name": "YouTube Title Analyzer",
      "description": "Analyze titles for engagement potential and SEO performance.",
      "category": "titles",
      "icon": "edit"
    }
  ]
}

GET /tools/:slug

Returns detailed information about a single tool identified by its URL-friendly slug. The response includes the same fields as the list endpoint plus additional metadata such as features and related tools.

Response — 200 OK 
{
  "data": {
    "id": "thumbnail-tester",
    "slug": "thumbnail-tester",
    "name": "Thumbnail Preview Tester",
    "description": "Preview and compare YouTube thumbnail variations in real time.",
    "category": "thumbnails",
    "icon": "image",
    "features": [
      "Side-by-side preview",
      "Device frame overlays",
      "Resolution checking",
      "Text readability scoring"
    ],
    "related": ["title-analyzer", "hook-library"]
  }
}

GET /docs/:slug

Returns the documentation page content for a given slug. The response includes the page title, body content as Markdown, last updated timestamp, and related page references.

Response — 200 OK 
{
  "data": {
    "slug": "getting-started",
    "title": "Getting Started",
    "body": "# Getting Started\n\nWelcome to Creator Studios...",
    "updated_at": "2026-05-15T10:30:00Z",
    "related": ["faq", "changelog"]
  }
}

Authentication

Currently, all read endpoints are publicly accessible and do not require authentication. This allows you to explore the API and build prototypes without any setup.

In a future release, we will introduce API key authentication for write and admin endpoints. When implemented, you will pass your API key in the Authorization header:

Future format 
Authorization: Bearer YOUR_API_KEY

API keys will be generated from the user settings dashboard. For now, no header is required.

Rate Limiting

To ensure fair usage and stability for all users, the API enforces rate limits on a per-IP basis:

  • Limit: 100 requests per hour
  • Window: Rolling 60-minute window
  • Scope: Per IP address

When you exceed the rate limit, the API returns a 429 Too Many Requests status code. The response includes a Retry-After header indicating the number of seconds to wait before making another request.

Rate limit response — 429 
HTTP/1.1 429 Too Many Requests
Retry-After: 3600
Content-Type: application/json

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Rate limit exceeded. Please wait before making additional requests."
  }
}

Response Format

All API responses use JSON and follow a consistent structure. Successful responses wrap the returned data in a data key. Error responses include an error object with a machine-readable code and a human-readable message.

Success Response

Example success 
HTTP/1.1 200 OK
Content-Type: application/json

{
  "data": { ... }
}

Error Response

Example error 
HTTP/1.1 404 Not Found
Content-Type: application/json

{
  "error": {
    "code": "not_found",
    "message": "The requested resource could not be found."
  }
}

Examples

Below are curl examples for each endpoint. You can run these commands directly in your terminal to verify the API is working.

List all tools

Shell — curl 
curl https://api.creatorstudios.org/v1/tools

Get a specific tool

Shell — curl 
curl https://api.creatorstudios.org/v1/tools/thumbnail-tester

Get documentation by slug

Shell — curl 
curl https://api.creatorstudios.org/v1/docs/getting-started
💬 Feedback