ContentStudio API

ContentStudio’s API lets you manage workspaces, social accounts, and posts programmatically.

This guide provides an overview of the available endpoints and explains how to authenticate and use the API effectively.

By using your API key, you can connect ContentStudio with integrations like Zapier, Make.com, or custom applications.


How to Get Your ContentStudio API Key

1 Click on your profile picture in the top-right corner, and select the API Key option from the dropdown menu.

2 Click on Generate API Key and copy your unique API key.

You can now use this API key wherever required, such as in Zapier, Make.com, or when connecting with other integrations.

3 Click on the three dots next to your API key. You’ll see two options:

  • Regenerate: Create a new API key if your current one is compromised or you want to reset access.
  • Revoke: Permanently disable the existing API key if it’s no longer needed.


Authentication

Authenticate all requests with your API key in the request header.

Header format:

X-API-Key: <YOUR_API_KEY>
  

Example using curl:

curl -H "X-API-Key: <YOUR_API_KEY>" \
https://qa-api.contentstudio.io/v1/me
  

This authenticates your request and grants access to API endpoints.


Endpoints

Get Authenticated User

Retrieve information about the currently authenticated user.

Endpoint: GET /api/v1/me

curl Example:

curl -X GET "https://qa-api.contentstudio.io/v1/me" \
  -H "X-API-Key: <YOUR_API_KEY>"

Get Workspaces

Fetch a list of workspaces linked to your account.

Endpoint: GET /api/v1/workspaces

curl Example:

curl -X GET "https://qa-api.contentstudio.io/v1/workspaces?page=1&per_page=10" \
  -H "X-API-Key: <YOUR_API_KEY>"

Get Social Accounts

Retrieve connected social accounts for a workspace.

Endpoint: GET /api/v1/workspaces/{workspace_id}/accounts

curl Example:

curl -X GET "https://qa-api.contentstudio.io/v1/workspaces/{workspace_id}/accounts?platform=facebook,instagram" \
  -H "X-API-Key: <YOUR_API_KEY>"

Get Posts

Fetch posts from a workspace with filtering options (draft, scheduled, published, etc.).

Endpoint: GET /api/v1/workspaces/{workspace_id}/posts

curl Example:

curl -X GET "https://qa-api.contentstudio.io/v1/workspaces/{workspace_id}/posts?status[]=scheduled&per_page=10" \
  -H "X-API-Key: <YOUR_API_KEY>"

Create Post

Create and schedule a new post.

Endpoint: POST /api/v1/workspaces/{workspace_id}/posts

curl Example:

curl -X POST "https://qa-api.contentstudio.io/v1/workspaces/{workspace_id}/posts" \
  -H "X-API-Key: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
        "content": {
          "text": "Check out our latest product launch!",
          "media": {
            "images": ["https://example.com/image1.jpg"],
            "video": "https://example.com/video.mp4"
          }
        },
        "accounts": ["{account_id_1}", "{account_id_2}"],
        "scheduling": {
          "publish_type": "scheduled",
          "scheduled_at": "2025-12-25 15:30:00"
        }
      }'

Delete Post

Delete a post by ID.

Endpoint: DELETE /api/v1/workspaces/{workspace_id}/posts/{post_id}

curl Example:

curl -X DELETE "https://qa-api.contentstudio.io/v1/workspaces/{workspace_id}/posts/{post_id}" \
  -H "X-API-Key: <YOUR_API_KEY>"

Best Practices

  • Keep it safe: Never share your API key publicly.
  • Rotate if needed: You can revoke and regenerate keys anytime from settings.
  • Use only where needed: Paste the key only into trusted platforms or integrations.


Related Articles

FAQs

Q1. Where can I use the ContentStudio API key?

You can use it to authenticate integrations with tools like Zapier, Make.com, or directly when making API requests.

Q2. Can I generate multiple API keys?

No, only one active API key is available per account at a time.

Q3. What happens if I regenerate my API key?

The old key will stop working immediately, and you’ll need to update the new key anywhere you were using it (Zapier, Make.com, custom apps, etc.).

Q4. What happens if I revoke my API key?

Revoking permanently disables the key. Any integrations using it will stop working until you generate a new one.

Q5. Is my API key private?

Yes. Treat it like a password — never share it publicly or expose it in client-side code.


Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us