Skip to navigation

Organizations

The organization a token acts in
View as MarkdownOpen in Claude

Every Modular DS resource belongs to an organization. A personal access token is bound to your membership in one organization, and every request made with it acts in that organization, with the role you have in it.

One organization per token

  • Listings only return resources of the token’s organization.
  • A resource of another organization answers 404, exactly as a resource that does not exist:
{
  "errors": [
    { "status": "404", "title": "Not Found", "detail": "Resource not found." }
  ],
  "jsonapi": { "version": "1.1" }
}

To work in several organizations, create one token in each of them.

Your role still applies

A token never does more than you could do in the dashboard. An action your role does not allow answers 403, and some resources you cannot see answer 404 instead so that their existence is not disclosed.

Public API switch and request quota

The organization must have the Public API enabled, and its request quota for the current billing period must not be used up. Otherwise every request answers 403 until the situation is resolved, with one of these details:

Situationdetail
The Public API is disabledThe Public API is disabled for this organization. The organization owner can enable it in the organization settings.
The quota for the billing period is used upThe Public API request quota for this billing period is used up. Enable the Public API requests overage to keep using it.

The switch is checked first: a disabled Public API answers with the first message even when the quota is also used up.