Brix

Brix Users API

The users API from Brix — 9 operation(s) for users.

GitHub OpenAPI

Operations 9

GET /v1/users List users #
PATCH /v1/users/{id} Update user #
POST /v1/users/{id}/deactivate Deactivate user #
POST /v1/users/{id}/erase Erase user under GDPR #
POST /v1/users/{id}/reactivate Reactivate user #
GET /v1/users/{id}/sessions List user sessions #
DELETE /v1/users/{id}/sessions/{sessionId} Revoke user session #
POST /v1/users/{id}/sessions/revoke-all Revoke all user sessions #
POST /v1/users/invite Invite user #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/brixsignage-com/openapi/brixsignage-com-users-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/brixsignage-com/json-schema/brixsignage-com-screen-schema.json
📊
JSONSchema
https://artifacts.apis.io/brixsignage-com/json-schema/brixsignage-com-media-asset-detail-schema.json
📊
JSONSchema
https://artifacts.apis.io/brixsignage-com/json-schema/brixsignage-com-media-asset-schema.json
📊
JSONSchema
https://artifacts.apis.io/brixsignage-com/json-schema/brixsignage-com-manifest-preview-schema.json
📊
JSONSchema
https://artifacts.apis.io/brixsignage-com/json-schema/brixsignage-com-media-asset-updated-schema.json
📊
JSONSchema
https://artifacts.apis.io/brixsignage-com/json-schema/brixsignage-com-workspace-prefs-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/brixsignage-com:brixsignage-com-users-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

brixsignage-com-users-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Brix Users API
  version: '1'
  summary: 'Control plane for Brix digital signage: screens, content, playlists, schedules, casts and emergencies.'
  description: 'Generated from the route table the API actually mounts

    (`apps/api/routes.snapshot.json`), the description each route is required to

    carry (`tests/contracts/route-registry.json`), and request/response schemas

    (`apps/api/src/openapi/`). CI enforces all three, so this document cannot list a

    route that does not exist or omit one that does.


    **Schemas.** 447 operations carry request and response schemas

    (`x-brix-schema: verified`). Each is checked in CI against the response the

    real handler returns — a missing, mistyped or undeclared field fails the build.

    The remaining operations are route-level only (`x-brix-schema: none`): their

    path, method, permission and purpose are exact, but the shape of `data` is not

    yet modelled, and we would rather say so than publish a schema that validates

    against nothing. Objects are open: a new field is not a breaking change.


    **Envelope.** Success bodies are `{ "data": … }`. Failures are

    `{ "error": "", "message": "…" }`, plus `requestId` on a 5xx.

    Many list routes page opt-in (see each operation): pass `?limit=` and

    follow `nextCursor` via `?cursor=` until it is null.


    **Authentication.** `Authorization: Bearer ` with an API key

    (`ak_…`, created in the console under Settings → API & MCP) or a user session. An

    API key carries a creator-chosen set of `resource.verb` permissions and may be

    pinned to one location''s subtree; a key can never be granted a permission its

    creator does not hold. The permission an operation needs is in

    `x-brix-permission` and in its security requirement.


    **Tenancy.** Every request resolves to one workspace. A resource belonging to

    another tenant returns 404, never 403, so a response never confirms that an

    account exists.


    **Rate limits.** A 429 carries `Retry-After`; a 503 `database_busy` means retry

    after the `Retry-After` interval.'
servers:
- url: https://api.brixsignage.com
  description: Production
security:
- bearerAuth: []
tags:


# --- truncated at 32 KB (34 KB total) ---
# Full source: https://artifacts.apis.io/brixsignage-com/openapi/brixsignage-com-users-api-openapi.yml