Developer integration

Quota Queue API commission workflow

Quota Queue is commission software with a developer API and an OpenAPI 3.1 spec: use scoped API keys to manage plans, deals, quotas, pay periods, and statements, queue commission recalculation, and receive signed webhooks when statements and disputes change.

Direct answer

Does Quota Queue integrate with Quota Queue API?

Yes. Quota Queue publishes a REST API described by an OpenAPI 3.1 document, a Streamable HTTP MCP server for AI agents, and outbound webhooks. The API covers plans and rules, assignments and quotas, deals, pay periods, statements, reports, and a recalculation endpoint. Webhooks deliver statement.locked, statement.approved, statement.paid, statement.reopened, dispute.opened, dispute.resolved, and deal.imported events signed with an HMAC-SHA256 X-QuotaQueue-Signature header.

Quota Queue API commission questions

Is there an API for commission calculation and webhooks?
Yes. POST /calculate queues commission recalculation for an open pay period using the same engine as the app, and outbound webhooks notify your systems when statements are locked, approved, paid, or reopened, when disputes open or resolve, and when deals are imported. API keys are available on Starter and Pro; outbound webhooks are a Pro capability.
Where is the OpenAPI spec?
The OpenAPI 3.1 document is public at https://quotaqueue.com/api/v1/openapi.json, with reference documentation at https://quotaqueue.com/docs/api.

What the connection does

Create scoped credentials

Workspace administrators can create read, write, or admin API keys and set expiration behavior.

Discover the contract

Use the public API documentation and OpenAPI document to inspect supported resources and request formats.

Build controlled handoffs

Send Bearer-authenticated requests without embedding a person’s browser session in an integration.

Plan and tier notes

  • API keys are available on Starter and Pro; outbound webhooks require Pro.
  • Keep raw keys secret; the complete key is revealed only when it is created.
  • Use the narrowest permission level and expiration period that fits the integration.