update_quota_values,
passing the id this call returns. The quota’s frequency, type and currency type
can only be changed afterwards on its page in the Qobra web app.
Quotas synchronized from an integration are not created here either — set
those up in the Qobra web app.
Available only where the Qobra write tools beta is enabled. Every write to the
live environment is recorded in the audit trail as the Qobra MCP agent;
writes to a sandbox are not audited.
Parameters
Body
Body
string
required
Display name of the quota, as people will read it in Qobra — ‘New
Business ARR’, ‘Number of demos booked’.
string
required
The period one target covers: monthly, quarterly, semesterly or annually.
It fixes the granularity every target value is written at (2026-03,
2026-Q1, 2026-S1, 2026), so it is the one field to get right before any
value is loaded. One of:
monthly, quarterly, semesterly,
annually.string
required
Unit of the target value: amount (monetary, carries a currency),
percentage, or float (a plain number — use it for counts, such as a
number of deals). One of:
amount, percentage, float.string
required
Default currency for an amount quota:
company (the company currency),
user (each user’s payment currency) or calculation (the user’s
calculation currency). Required even for a percentage or float quota,
where it is not meaningful — pass company there. One of: company,
user, calculation.string
Optional free-text note about what the quota targets.
string
Id of the sandbox to create the quota in — the id list_sandboxes
returns. Omit it to create the quota in the live environment. Only a
sandbox id is accepted here — never a sandbox name, and never the live
environment’s own id.
Response
Body
Body
object
The quota as it now exists — the same row list_quotas returns, so the id
can be reused straight away.