Quota Queue

Developers and agents

Quota Queue Developer Portal

Integrate commission operations through a documented REST API or connect an AI agent through the Quota Queue MCP server. Workspace administrators control access with scoped API keys, while public discovery endpoints explain capabilities without exposing customer data.

Quickstart

  1. Create a sandbox workspace, then open Settings → API keys as an administrator.
  2. Create the least-privilege read, write, or admin key needed by the integration.
  3. Read the OpenAPI document, choose an operation, and send the key in Authorization: Bearer ….
  4. Start with GET /api/v1/organization. Keep credentials out of URLs, prompts, repositories, and logs.

Documentation and machine discovery

API documentation

Authentication, endpoint discovery, and request conventions.

OpenAPI 3.1

Typed operations with unique operation IDs and response schemas.

Public capabilities

Unauthenticated API availability and discovery metadata.

MCP server card

Streamable HTTP transport, authentication, and tool manifest.

Agent instructions

When agents should use Quota Queue and how to call it safely.

Authentication

Workspace API-key provisioning and credential handling.

Sandbox, webhooks, and clients

New workspaces can use generated sample data as a safe sandbox before connecting production systems. The REST surface covers organizations, users, plans, rules, assignments, deals, pay periods, statements, reports, integrations, and calculations. Quota Queue also provides outbound webhook configuration in the authenticated application, a zero-dependency CLI, and a stdio MCP server for local agent clients.

The hosted MCP endpoint at https://quotaqueue.com/mcp uses Streamable HTTP and the same Bearer API key. Agents should inspect resources before mutation, preserve explicit commission terms, and read saved records back before claiming success.