Quota Management

Who this is for: both sides — Demand sets quotas, Supply reads them. When to use it: when controlling or respecting the composition of completes. What happens next: traffic is accepted only while matching quota cells have capacity.

A quota caps how many completes you accept for a given respondent segment (for example, "200 completes from women aged 25–34"). Quotas keep a study representative and prevent over-delivery.

Demand side — defining quotas

Action	Endpoint
Create a quota	createQuota
Read quotas	getQuota
Activate / deactivate a quota	updateInactiveActiveQuota

Define quotas after creating the project and before going live. Deactivating a full or unwanted cell stops new completes against it without deleting history.

Supply side — respecting quotas

Action	Endpoint
Read a survey's quotas	GetSurveyQuotas
Read qualifications	GetSurveyQualifications

Before sending a respondent, check that a matching quota cell is open. Respondents who match a full cell are returned as overquota at redirect — see Redirect Handling.

 respondent ──▶ matches quota cell? ──▶ open?  ──▶ enter survey
                       │                   │
                       └─ no match ────────┴─ full ─▶ overquota redirect

tip

Poll quotas periodically while fielding — cells fill in real time as completes land across all suppliers.