Welcome to DeskDay!

Introduction to the DeskDay API

The DeskDay REST API lets you interact with your DeskDay account programmatically — create and manage tickets, sync customer and user records, track time, handle billing, monitor SLAs, and receive real-time event notifications. Use it to connect DeskDay to your own tools, automate routine work, and keep external systems in sync.
The API is organized around predictable, resource-based URLs, accepts and returns JSON, and uses standard HTTP verbs (GET, POST, PATCH, DELETE) and response codes.

What you can do with the APIs

The API is grouped into the following resources. Each links to its endpoints in the API Reference.

  • Tickets — The heart of the Conversational Service Desk. Create, retrieve, list, update, and close tickets, and list a ticket's attachments.
  • Customers — Manage the customer accounts you support. Create, retrieve, list, and update customers, and list a customer's sites.
  • Users — Manage customer end-users. Create, retrieve, list, and update end-user records.
  • Time entries — Log billable and non-billable work against tickets. Create, retrieve, list, and update time entries.
  • SLA — Monitor service-level commitments. Check live SLA status for a ticket, bulk SLA status for up to 50 tickets, and SLA statistics.
  • Webhooks — Get notified in real time instead of polling. Create, list, retrieve, update, and delete webhook subscriptions.
  • Reference data — Look up the supporting values your requests depend on: boards, ticket types, sub-types, statuses, tags, work roles, work types, countries, and states.

Authentication

The DeskDay API uses bearer-token authentication. Include your token in the Authorization header on every request:

Authorization: Bearer <YOUR_API_TOKEN>

Requests without a valid token are rejected.

📘 Generating a token

Ready to Start?

  • Get your credentials. Generate an API token from your DeskDay account.
  • Make your first call. Use the API Reference to try an endpoint — listing tickets or customers is a good place to start. Every endpoint includes sample requests and responses you can run directly from the docs.
  • Automate with webhooks. Once you're reading and writing data, subscribe to webhooks to react to events in real time.

Explore the full API Reference for the details of every endpoint, including parameters, example requests, and responses.