Set customer-unit cap (by external customer id)
Sets the cap on this customer unit for one credits currency. Returns changed: false without creating a version when the effective timeline is unchanged; otherwise records a new version, preserving earlier rows. The newest version wins where they overlap. effectiveFrom controls applicability; schedule defines monthly UTC boundaries independently. Omit schedule to inherit the version covering effectiveFrom, or use the creation-time UTC day if none applies. Select the currency with creditsCurrencyId in the body; it may be omitted only when the organization has exactly one credits currency. A cap covers the unit and every unit beneath it, so a cap on the customer’s root unit covers every unit of that customer; spend from a signal that names no unit counts toward no cap. 404 when the customer or the unit does not exist. 409 for customers on seat-based billing, a deleted unit (CUSTOMER_UNIT_DELETED) or a draft (CUSTOMER_UNIT_DRAFT). Addresses the customer by your external customer id.
Authentication
Path parameters
Customer ID from your system, stored on Paid as the customer's externalId.
Your own id for the unit (its externalId), unique within this customer.
Request
Monthly UTC periods, with boundaries defined by schedule.
Omit to inherit the schedule in force at effectiveFrom. If none applies, use the creation-time UTC day. An explicit change counts spend from the new schedule’s ordinary period start, including earlier spend.
The credits currency to cap. Omit it only when the organization has exactly one credits currency, which is then used; otherwise it is required.
ISO 8601 timestamp. When the cap starts applying, independently of its schedule. Defaults to now. Spend earlier in the schedule’s current period still counts.
Response
Your own id for the unit (its externalId), the identifier the unit and cap routes take.
The credits currency the cap was set on: the requested creditsCurrencyId, or the organization's only credits currency when it was omitted.
The new version, or the existing version covering the requested effectiveFrom when changed is false. New versions are open; an existing version may have a finite end.
Usage in the current period, when the returned version is in force now and usage is available; otherwise null.