Connectors API
Connectors endpoints in the Brix REST API for digital signage: 2 operations (GET, POST). Each lists its path, auth, required permission and a curl example.
View as Markdown · For AI agents: the full docs index is at /llms.txt
Base URL https://api.brixsignage.com. Send Authorization: Bearer $BRIX_API_KEY unless an operation says Auth: none or Auth: no API key. The Permission line names what the key must hold. See Authentication and scopes, Errors and rate limits and Pagination.
Every 4xx and 5xx response below returns this body:
| Field | Type | Description |
|---|---|---|
error | string | Machine-readable code: unauthorized, forbidden, not_found, validation_error, conflict, rate_limited, internal_error, … |
message | string | Human-readable explanation. Safe to show an operator. |
requestId | string | Present on 5xx: quote it to support. |
GET /v1/connectors
List the data-source connector types: the type to use when you create a data source, its label and category, and whether it is available yet.
curl "https://api.brixsignage.com/v1/connectors" \
-H "Authorization: Bearer $BRIX_API_KEY"Response 200: Success.
| Field | Type | Description |
|---|---|---|
data | array of Connector | |
data[].type | string | The value for a data source's type (http-json, csv, google-sheets, …). |
data[].label | string | |
data[].category | string | Group the connector is listed under (generic, celebrations, …). |
data[].available | boolean | False for a connector that is listed as coming soon and cannot be used yet. |
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/connectors/probe
Test whether the platform can reach a given endpoint, behind the Test connection action used before creating a data source. The request is made from the server rather than the browser. Requests to private or internal network addresses are blocked.
Sends a GET to the URL from the server and returns the status and the start of the body. Rate limited to 20 calls a minute.
Notes.
- A URL that cannot be reached is not an HTTP error: the answer is 200 with ok: false, status: 0 and error.
- A blocked private or internal address answers 400 with the { data: { ok: false, status: 0, error } } body, not the usual error body.
Request body: application/json
| Field | Type | Required | Description |
|---|---|---|---|
url | string | yes | An http(s) URL on the public internet. |
token | string | no | Sent as Authorization: Bearer <token>. Not stored. |
curl -X POST "https://api.brixsignage.com/v1/connectors/probe" \
-H "Authorization: Bearer $BRIX_API_KEY" \
-H "Content-Type: application/json"Response 200: Success.
| Field | Type | Description |
|---|---|---|
data | object | object |
Response 400: bad_request: the URL is not http(s). A private or internal address also answers 400, with the data body (ok: false, status: 0, error) instead of an error body.
Response 401: Missing, expired or revoked bearer token.
Response 403: The token lacks the permission this operation needs (see x-brix-permission).
Response 429: More than 20 calls in a minute.
Response 5XX: Server error. The body carries a requestId to quote to support.