Brivio API reference
Cabinet

Cabinet requests access to a managed client — creates a PENDING grant the client admin approves in the app. 201 created, 200 when a live grant already exists; 403 not_a_cabinet; 422 client_not_linked. (scope: grants:write)

POST
/cabinet/access-grants

Authorization

bearerAuth
headerAuthorizationBearer <token>

API key as Bearer token

Request Body

application/json
  1. body
client_org_id*string

A client this cabinet actively manages

Formatuuid

Response Body

OK

application/json
  1. response
data?
error?null
curl -X POST "https://example.com/cabinet/access-grants" \  -H "Content-Type: application/json" \  -d '{    "client_org_id": "9aa3dfe7-3f4d-43e2-a858-0015d7ac15be"  }'
{  "data": {    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "status": "pending",    "client_org_id": "9aa3dfe7-3f4d-43e2-a858-0015d7ac15be",    "created": true  },  "error": null}

SPV / e-Factura status of every client the key’s organisation manages (accounting practice) — per client: last sync, unread (critical flagged), rejected uploads, invoices within 2 working days of the legal window, invoices past it, and the ANAF connection state and expiry. Read-only; the client set is the cabinet’s active managed companies. (scope: efactura:read) GET

Previous Page

Revoke an access grant — either the cabinet or the client may. 409 invalid_transition when already revoked. (scope: grants:write) POST

Next Page