MakeTheQueue has a public REST API versioned at /api/v1/. Every action the admin app performs, from listing queues to fetching analytics, is available as an HTTP endpoint so you can integrate with your POS, CRM, or internal tools.

API access is included on every paid plan. On the Free plan, API requests return a 403 with an upgrade message.

How your API key works

Each organization gets an API key automatically when the account is created. The key looks like mtq_ followed by a 32-character hex string. Treat it like a password: anyone with the key can act on your account.

  1. Your key is generated once, at sign-up.
  2. There is no in-app button to view or regenerate it today.
  3. If you need to retrieve or rotate your key, contact support and we will help.

Authentication

Send your key in the x-api-key header on every request:

x-api-key: mtq_your_key_here

Requests without a valid key get a 401 response. A valid key on the Free plan gets a 403 with an upgrade message, since API access is a paid feature.

Useful endpoints to start with

  1. GET /api/v1/queues. List the queues in your organization, optionally filtered by location.
  2. POST /api/v1/queues/:queueId/join. Add a customer to a queue from your own form or app.
  3. GET /api/v1/locations. List your locations and their settings.
  4. GET /api/v1/analytics/summary. Pull totals for served, cancelled, average wait, and more.

All endpoints accept and return JSON.

Common problems

  • 401 Unauthorized. Double-check that the key is in the x-api-key header and starts with mtq_.
  • 403 with an upgrade message. The key is valid but your plan doesn't include API access. Upgrade to a paid plan.
  • I cannot find my API key. There is no UI to view or regenerate it. Contact support to retrieve your current key.
  • My key was shared by accident. Contact support right away so we can rotate it.
  • 404 on an endpoint. Make sure the path starts with /api/v1/ and that the queue or location ID is correct.

Related articles