Upsert assignments
Changed onBatched create-or-update of capability assignments. Existing assignments matched by (entityId, capabilityId) are updated; new pairs are created. On update, omitted fields (usageLimit, cadence) are preserved; on create both are required by the governance service.
Request
- Base URLhttps://api.stigg.io
- URLhttps://api.stigg.io/api/v1-beta/customers/{id}/assignments
- AuthAPI key in header X-API-KEY
Path parameters
The customer identifier (owner) the assignments belong to
Headers
Account ID — optional when authenticating with a user JWT (Bearer token); falls back to the user's first membership. Ignored for API-key auth.
Environment ID — required when authenticating with a user JWT (Bearer token) on environment-scoped endpoints. Ignored for API-key auth (env is intrinsic to the key).
Request body
Response
Assignments after upsert.
Changes
- warning
added the new
ContractNotFoundenum value to theresponse property for the response status
- warning
- warning
added the new
CreditOveragePriceCurrencyNotFoundenum value to theresponse property for the response status - warning
added the new
InvalidCreditOverageBillingModelenum value to theresponse property for the response status - warning
added the new
InvoicePreviewNotAvailableForDraftContractenum value to theresponse property for the response status - warning
added the new
OveragePriceNotSupportedOnAddonenum value to theresponse property for the response status - warning
added the new
OveragePriceRequiresUsageLimitenum value to theresponse property for the response status
- warning