CMA (Content Management API)

Last updated: July 3, 2026

The CMA (Content Management API) is a management API that creates, reads, updates, and deletes the content and settings of a Space. Anything you do in the content studio (writing content, publishing, managing members and roles, issuing tokens, and so on) can be done from code in the same way. Delivering published content to visitors through a read-only API is handled separately by CDA.

The base URL is https://cma.weegloo.com/v1. The calling identity is a Weegloo User (a Weegloo platform account). From servers, CI, and scripts you send a Personal Access Token as the Bearer token, and from browser admin UIs you send the token issued by the content studio login flow. Its tokens are not compatible with ACMA, which operates under the identity of a member (ServiceUser) who signed up for the product.

Common behavior

The following applies across all CMA resources. Each resource page assumes this behavior and covers only its own specifics.

  • Full CRUD. Create (POST), read (GET), update (PUT/PATCH), and delete (DELETE) are all supported. Unlike read-only CDA, writing and publishing happen here.
  • Updates require a version header. When you update a resource, you must put the current resource's sys.version value in the x-weegloo-version header. This prevents you from overwriting a version that someone else changed first.
  • Partial updates use PATCH. To change only some fields, send a PATCH with an RFC 6902 JSON Patch body. For this, the request Content-Type is application/json-patch+json. To replace the whole body, use PUT.
  • It must be published to be delivered. Content, Media, and Content Type are delivered to CDA only after you create or change them in CMA and then Publish. A pre-publish Draft or unpublished changes are visible in the content studio and in CMA but do not enter the delivery path.
  • Response media type. The response Content-Type is application/vnd.com.weegloo.v1+json;charset=UTF-8. Sending Accept: application/json on a request can cause negotiation to fail, so omit Accept or use the same vendor type.

Common conventions such as list query parameters (limit, order, include, select, filters, cursor pagination), the sys structure, and error codes are covered in Common Query Parameters, System Properties (sys), Conventions, and Errors.

Resources

Content

  • Content Type: Defines the template (schema) that content follows. It sets the field composition, types, whether they are multilingual, whether they are required, and validation rules.
  • Content: Creates, updates, and publishes a single piece of actual data produced from a Content Type.
  • Media: Manages the resource that holds uploaded files (images, documents, and so on).
  • Tag: Manages short labels that classify Content or Media.
  • Locale: Manages the language settings a Space supports (code, whether it is the default, and fallbackCode).

Spaces and organizations, permissions

  • Organization: The top-level container that holds Spaces. The subscription plan (plan) and memberships are managed at this level.
  • Organization Membership: Represents which Organization a person belongs to and with what permissions, and brings in new members by email invitation.
  • Space: The workspace where all of a project's content is held.
  • Space Membership: Represents which Space a user belongs to and with which SpaceRoles.
  • SpaceRole: A bundle of permissions given to a Space member. It holds per-resource actions (read, create, edit, delete, publish) and scope filters.

Tokens

  • Personal Access Token: A long-lived token a Weegloo User uses to call CMA, Upload, and CDA with their own permissions from servers, CI, and scripts.
  • Delivery Access Token: A read token used to read published content from CDA. When issued, it is bound to a single SpaceRole that sets its read scope.

Product members (ServiceUser)

  • ServiceLogin: The setting by which a Space lets the end-users (ServiceUser) of its own product sign up and log in via OAuth.
  • ServiceUserRole: A bundle of permissions given to a ServiceUser who signed up for the product. It applies to ACMA/ACDA.
  • ServiceUser: A product end-user who signed up through ServiceLogin, that is, a member account.

Deployment and integration

  • Web Hosting: A resource that serves a built static website at a {subdomain}.weegloo.app address.
  • Webhook: A setting that sends an HTTP request to a designated external URL when something happens in a Space (for example, Content creation or publishing).
  • CDA: The read-only API that delivers published content to visitors.
  • ACMA: The version that performs the same management work under a member (ServiceUser) identity.
  • Upload: The upload API that uploads a file and then connects the result to Media creation.