Workspaces

Overview

Maeve Social organizes API resources in a hierarchy:

Organization
  Workspace
    Integrations
    Content
    Media
    Analytics
    Inbox

An organization is your top-level account. A workspace contains connected social accounts, scheduled content, media, labels, campaigns, and collaboration workflows.

Discovering workspaces

The workspaces endpoint is the starting point for API usage:

curl https://api.maevesocial.com/v1/workspaces \
  -H "Authorization: Bearer $MAEVE_API_KEY"

{
  "data": [
    {
      "id": "workspace-uuid",
      "name": "Main Workspace",
      "slug": "main-workspace",
      "organizationId": "organization-uuid",
      "role": "manager"
    }
  ],
  "meta": null
}

With API key authentication, this endpoint only returns workspaces explicitly granted to the key.

Workspace-scoped routes

After you have a workspace ID, pass it in the route path:

curl https://api.maevesocial.com/v1/workspaces/WORKSPACE_ID/content \
  -H "Authorization: Bearer $MAEVE_API_KEY"

The main workspace-scoped route groups are:

API key workspace grants

Maeve API keys are workspace-granted. A key can access only the workspace IDs it was granted when it was created. A key cannot be used to create another key.

To grant access to additional workspaces, create a new key with the desired workspaceIds.

Roles

Workspace roles determine what a user or session-authenticated request can do. API keys inherit their creator's allowed workspace grants at creation time and are still checked against workspace access.

Organization owners and admins resolve to manager-level workspace access for many workspace APIs.