dsigns documentation
Connect n8n or an AI client
Read player status, edit drafts and publish approved content from your existing tools.
Set up REST access
- Open Settings → Integrations → MCP & API. Choose the customer and create a named API key with
players:readto start. - Save it in your tool’s credential store. In n8n, use HTTP Header Auth: name
Authorization, valueBearer YOUR_KEY. - Send a GET request to the address below. A successful response lists players inside the chosen customer.
GET https://dsigns.bitprecision.com/api/v1/players
Authorization: Bearer YOUR_KEYUse the API reference for request fields and required permissions. Add write permissions only for the operations you intend to run.
n8n examples
Import a workflow, attach your Header Auth credential to every HTTP node and replace the marked IDs. Examples import inactive and send no emails or chat messages. Review targets before running a write.
Preview and publish an approved player
The preview includes all assigned drafts. Inspect it before publishing.
Download workflow ↓Create a ten-minute screen override
Normal programming resumes when the downloaded action expires.
Download workflow ↓Retries and reporting
Send a unique Idempotency-Key for each JSON write. Reuse it when retrying the same request. If Activity says pending after a connection failure, check the target before using another key; the accepted action may already exist. Upload parts and completion reuse their upload IDs.
A successful request means saved or accepted. Offline players receive new content after reconnecting. Reported status does not confirm the physical screen’s picture.
Webhooks and alerts
Manage incoming and signed outgoing webhooks in Settings → Integrations → Webhooks. Failed outgoing deliveries need manual retry. Configure offline emails separately in Settings → General → Offline emails. For polling in n8n, use a Schedule Trigger and the read-only player-status workflow.