Account API

GET/v1/account

Returns the workspace plan, subscription status, screen pool size, trial or paid status, and onboarding progress. **Notes.** - email, emailVerifiedAt and verificationEmailLastSentAt describe the CALLING user; they are null for an API key. - On a workspace created before the onboarding step existed, a null prefs.onboardingCompletedAt is filled with the workspace's creation time (and saved).

curl "https://api.brixsignage.com/v1/account" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/billing-address

Returns the billing address on file with the billing provider: the country used to determine invoice tax, and, for the United States and Canada, the state and postal code. The response includes configured: false when no billing address has been set yet.

curl "https://api.brixsignage.com/v1/account/billing-address" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 5XX Server error. The body carries a `requestId` to quote to support.

PUT/v1/account/billing-address

Sets the workspace billing address. country is required and validated against the ISO 3166-1 country list. For the United States and Canada, stateCode and zip are also required. This replaces the entire address on file; you cannot update a single field. **Notes.** - Answers 400 (not 422) for an invalid address, unlike most validation errors.

Request body application/json

curl -X PUT "https://api.brixsignage.com/v1/account/billing-address" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 400 `invalid_country` or `state_required` (400, not 422).

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `no_customer`: billing is not set up yet.

Response 502 The billing provider did not answer; nothing changed.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/billing-mode

Switches the workspace between automatic card charging (auto) and invoice billing (invoice). Switching to invoice billing requires a signed-in user with a verified work email address, so an API key can only switch to automatic charging.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/billing-mode" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 `user_required`: switching to `invoice` needs a signed-in user with a verified work email, so an API key can switch only to `auto`. Also: You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `email_unverified`, `work_email_required`, `billing_not_configured`, or `under_contract`.

Response 422 `mode` is not `auto` or `invoice`.

Response 502 The billing provider did not answer; nothing changed.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/cancel

Submits a cancellation request with a reason. Choosing the reason "Seasonal Business" together with a restartDate pauses the account instead of cancelling it. Any other reason schedules cancellation for a fixed number of days after the request. Cancellation can be reversed at any time before it takes effect by calling the reactivate operation.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/cancel" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 No such workspace.

Response 409 `payment_required` (unpaid invoice), `already_cancelled`, or `under_contract` (an agreed term; contact Brix).

Response 422 `reason` missing, or a bad `restartDate`.

Response 502 The billing provider did not answer; nothing changed.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/cancel-deletion

Stops a scheduled permanent deletion of the workspace before it happens. Call this any time before the deletion date to keep the account and its data. **Notes.** - The account stays cancelled; reactivate it separately.

curl -X POST "https://api.brixsignage.com/v1/account/cancel-deletion" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `not_pending_deletion`.

Response 5XX Server error. The body carries a `requestId` to quote to support.

PATCH/v1/account/contract/renewal

Sets whether the workspace's current contract term renews automatically or ends at term expiry. Choosing not to renew voids any unpaid renewal invoice; choosing to renew allows Brix to invoice the next term automatically. Returns 409 if the workspace has no fixed term, and 404 for white-label workspaces, where this setting does not apply. **Notes.** - Turning auto-renew off voids an unpaid renewal invoice.

Request body application/json

curl -X PATCH "https://api.brixsignage.com/v1/account/contract/renewal" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 A workspace billed by a partner.

Response 409 `no_term` (no agreed term), or a term that cannot change here.

Response 422 `renewal` is not `renew` or `non_renewing`.

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/data-inventory

Returns, for every category of data Brix holds about the workspace, what it is, whether it identifies a person, how long it is kept, whether it is included in a data export, and whether it is deleted when the account is closed. Pass ?counts=1 to include a row count for each category.

curl "https://api.brixsignage.com/v1/account/data-inventory" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/downgrade-monthly

Switches the workspace from annual to monthly billing at the end of the current annual term. Nothing is charged or refunded now.

curl -X POST "https://api.brixsignage.com/v1/account/downgrade-monthly" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `no_subscription`, `already_monthly`, or `under_contract`.

Response 502 The switch could not be scheduled.

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/encryption-key

Returns whether the workspace can use its own encryption key in Azure Key Vault, what that key covers, its identifier, its status, and the progress of re-encrypting existing data under it.

curl "https://api.brixsignage.com/v1/account/encryption-key" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 5XX Server error. The body carries a `requestId` to quote to support.

PUT/v1/account/encryption-key

Enables encryption with the workspace's own key in Azure Key Vault. Brix verifies the key, generates and wraps a data key, and starts re-encrypting existing secrets under it. Every new secret created after this call is protected with the customer's key.

Request body application/json

curl -X PUT "https://api.brixsignage.com/v1/account/encryption-key" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 201 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `conflict` (a key is already set; turn it off first) or `key_check_failed`.

Response 422 Bad `tenantId` or `keyId`.

Response 503 `not_available` on this platform.

Response 5XX Server error. The body carries a `requestId` to quote to support.

DELETE/v1/account/encryption-key

Disables the workspace's customer-managed encryption key. Every secret currently protected by that key is first moved back under the Brix-managed key, so nothing becomes unreadable, and only then is the key record removed. Returns 409 if the customer-managed key can no longer be reached. **Notes.** - key is null when the first pass moved every secret back; otherwise it shows disabling until the hourly pass finishes.

curl -X DELETE "https://api.brixsignage.com/v1/account/encryption-key" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 No key is set.

Response 409 `key_unavailable`: the vault did not answer, so secrets cannot be moved back.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/encryption-key/verify

Performs a dry run against the workspace's own encryption key: it wraps and unwraps a random test value to confirm the key still works. Nothing is stored or changed.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/encryption-key/verify" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `key_check_failed`: the vault refused (`kind` says why).

Response 422 Bad `tenantId` or `keyId`.

Response 503 `not_available` on this platform.

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/export

Returns a data export of the workspace as one downloadable file: the workspace record, its members, nine content tables and the last 365 days of activity-log events. Credentials are never included. Because the file holds every member's personal data, it requires permission to edit billing for the whole workspace. Brix does not email or store the export. For every table and the complete activity log, use the export manifest and its parts. **Notes.** - No { data } envelope: the body is the export file (Content-Disposition: attachment). - Credentials are never exported: their columns are kept with null or a [secret; not exported] / [encrypted; not exported] marker. - generatedBy.kind is user even when an API key made the export (and then userId is absent). - The complete export (every table, the whole audit log) is GET /v1/account/export/manifest and its parts.

curl "https://api.brixsignage.com/v1/account/export" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/export/manifest

Describes the contents of a full data export without downloading it: every table of workspace data with its row count, which tables are excluded from the export and why, and which fields are redacted and why. Use this to confirm what an export will and will not contain before downloading it.

curl "https://api.brixsignage.com/v1/account/export/manifest" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/export/part/{part}

Downloads one part of a full data export. Results are paged with a cursor rather than an offset, so rows are not skipped or duplicated if data changes while the export is running. Secret values are replaced with a marker rather than removed, so a withheld value can be told apart from one that was never set. Pass ?format=csv to receive the same data as CSV, encoded with a UTF-8 byte-order mark for compatibility with Excel and guarded against spreadsheet formula injection. Use the x-brix-next-cursor response header to fetch the next page. **Notes.** - Credentials are never exported: their columns are kept with null or a [secret; not exported] / [encrypted; not exported] marker (the manifest lists them in redactedColumns). - ?format=csv answers text/csv instead, with the cursor in the X-Brix-Next-Cursor header.

curl "https://api.brixsignage.com/v1/account/export/part/{part}" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 No such part.

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/invoices

Returns the workspace's invoice history, newest first: invoices Brix issued for an agreed term and invoices of the card subscription. The response includes configured: false when billing has not been set up yet.

curl "https://api.brixsignage.com/v1/account/invoices" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/invoices/{id}/file

Downloads the PDF file for one invoice belonging to the calling workspace. **Notes.** - For an invoice Brix issued, when the PDF cannot be drawn the route answers 302 to the invoice's web page instead.

curl "https://api.brixsignage.com/v1/account/invoices/{id}/file" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 Not an invoice of this workspace.

Response 502 The billing provider did not answer; nothing changed.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/invoices/{id}/pay-link

Creates a shareable payment link for one invoice, which can be paid by card or ACH bank transfer. The link can optionally be emailed directly, for example to forward to a finance team. **Notes.** - For an invoice Brix issued, email is ignored and emailed is always false.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/invoices/{id}/pay-link" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 Not an invoice of this workspace.

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/invoices/{id}/pdf

Returns a short-lived download URL for one invoice's PDF. Brix confirms the invoice belongs to the calling workspace before returning the link.

curl "https://api.brixsignage.com/v1/account/invoices/{id}/pdf" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 Not an invoice of this workspace (invoices Brix issued have no link here; use `/file`).

Response 502 The billing provider did not answer; nothing changed.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/invoices/pay-all-link

Creates one shareable link that lets whoever receives it pay all of the workspace's outstanding invoices at once.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/invoices/pay-all-link" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `billing_not_configured`.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/invoices/pay-links-outstanding

Creates a separate hosted payment link for every invoice currently outstanding on the workspace. **Notes.** - Covers the card subscription's invoices only, not invoices Brix issued.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/invoices/pay-links-outstanding" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `billing_not_configured`.

Response 502 The billing provider did not answer; nothing changed.

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/limits

Returns the workspace's API usage limits: the number of requests allowed per minute, the time window, and confirmation that the limit is counted per workspace across all API keys rather than per key. Also returns the RateLimit-* response headers to expect, and the delivery, retry, and retention behavior for webhooks. Use this before building an integration to size your request rate correctly.

curl "https://api.brixsignage.com/v1/account/limits" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/me-prefs

Returns preferences in three layers: workspace (the shared defaults), user (only the values the calling user has changed; empty for an API key), and effective (the merged result to use for display). **Notes.** - user is returned as saved: the per-user write does not check its keys or values.

curl "https://api.brixsignage.com/v1/account/me-prefs" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 The token lacks the permission this operation needs (see `x-brix-permission`).

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/onboarding

Finishes workspace onboarding in a single call: renames the workspace to the given name, records the industry and complexity tier, marks onboarding as complete, and seeds a starter set of ready-to-play content tailored to the chosen industry. Combining these into one call ensures the completion flag and the seeded content are never out of sync. **Notes.** - Every call adds the starter content again; it is not idempotent. - tier is stored as sent without a check.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/onboarding" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 422 Unknown `industry`.

Response 5XX Server error. The body carries a `requestId` to quote to support.

DELETE/v1/account/payment-card

Removes the workspace's saved card. If the payment option was set to card, it reverts to invoice billing. **Notes.** - When the payment option was card, it goes back to invoice.

curl -X DELETE "https://api.brixsignage.com/v1/account/payment-card" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 A workspace billed by a partner.

Response 409 `not_brix_billed`.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/payment-card/complete

Saves the card from a finished hosted card-setup session, given its sessionId. Brix re-reads the session from the payment provider and confirms it belongs to the calling workspace, returning 404 otherwise. The same result also happens automatically when the payment provider notifies Brix that the session completed.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/payment-card/complete" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 Not a card session of this workspace.

Response 409 `not_brix_billed`.

Response 422 `sessionId` missing or malformed.

Response 502 The session could not be read.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/payment-card/setup

Starts adding or replacing the saved card for a workspace billed directly by Brix. Returns a hosted checkout URL where the card is entered, unless useLastPaid: true is passed and the payment provider already holds a card that was last used to pay this workspace, in which case that card is saved directly. Returns 409 if the workspace is not billed directly by Brix, and 404 for white-label workspaces.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/payment-card/setup" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 A workspace billed by a partner.

Response 409 `not_brix_billed`, or `card_unavailable`.

Response 502 The card page could not be opened.

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/payment-methods

Returns the workspace's saved payment methods, including cards and ACH bank accounts. When there are two or more methods and none is the backup, one method that is not the primary is made the backup. **Notes.** - A read that can write: with two or more methods and no backup, the handler makes one non-primary method the backup and records it in the audit log.

curl "https://api.brixsignage.com/v1/account/payment-methods" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/payment-methods/{id}/role

Sets a saved payment method as the primary or backup method for the workspace.

Request body application/json

curl -X POST "https://api.brixsignage.com/v1/account/payment-methods/{id}/role" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 Not one of this workspace's payment methods.

Response 409 `billing_not_configured`.

Response 422 Bad `role`.

Response 502 The billing provider did not answer; nothing changed.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/payment-methods/manage-url

Returns a hosted page URL where the workspace can add, replace, or remove a saved card or bank account.

curl -X POST "https://api.brixsignage.com/v1/account/payment-methods/manage-url" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `billing_not_configured`.

Response 502 The billing provider did not answer; nothing changed.

Response 5XX Server error. The body carries a `requestId` to quote to support.

PATCH/v1/account/payment-option

Sets how a workspace billed directly by Brix pays: card or invoice. Choosing card requires a saved card and returns 409 if none exists; every invoice Brix issues is then charged to that card automatically. Returns 409 if the workspace is billed through the billing provider instead, and 404 for white-label workspaces.

Request body application/json

curl -X PATCH "https://api.brixsignage.com/v1/account/payment-option" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 404 A workspace billed by a partner.

Response 409 `not_brix_billed`, or `card_required` (save a card first).

Response 422 Bad `option`.

Response 5XX Server error. The body carries a `requestId` to quote to support.

PATCH/v1/account/prefs

Updates workspace-level preferences such as locale, time zone, date and number formats, brand kit, and plan tier. Any field you include is overwritten; fields you omit keep their current value.

Request body application/json

curl -X PATCH "https://api.brixsignage.com/v1/account/prefs" \
  -H "Authorization: Bearer $BRIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"timeFormat":"24h","timeZone":"America/Chicago"}'

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 422 `sso_not_configured`, `two_factor_not_enrolled`, or a PIN that is not 4–8 digits.

Response 5XX Server error. The body carries a `requestId` to quote to support.

POST/v1/account/reactivate

Reverses a scheduled cancellation, or resumes an account that was paused for seasonal closure.

curl -X POST "https://api.brixsignage.com/v1/account/reactivate" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

Response 401 Missing, expired or revoked bearer token.

Response 403 You do not hold the permission for the whole workspace (a grant at one location is not enough).

Response 409 `already_active`, `pending_deletion`, `payment_required`, `payment_method_required`, `not_reactivatable`, or `under_contract`.

Response 502 The billing provider did not answer; nothing changed.

Response 5XX Server error. The body carries a `requestId` to quote to support.

GET/v1/account/retention

Returns the workspace's data retention schedule: every data stream that can be governed, the retention window currently in effect for it, and the allowed range for that window.

curl "https://api.brixsignage.com/v1/account/retention" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.