Change an install's scopes or rate limit
patch/v1/tenants/{tenant_id}/installs/{install_id}
Requires an API key
Scopes are replaced with a fresh consent (scopes and consent_revision). Only Ivora administrators change rate_limit_per_minute (default 120 requests a minute for each install).
Path parameters
- tenant_idintegerRequired
- install_idstringRequiredPattern
^ins_[0-9a-f]{32}$
Request body
- scopesarray of string | nullReplaces the granted scopes (with consent_revision).
- consent_revisioninteger | nullMinimum 1
- rate_limit_per_minuteinteger | nullIvora administrators only: the install's own requests a minute (default 120).Minimum 1 · Maximum 100000
Returns · 200
- idstringRequired
- app_idstringRequired
- app_namestring | null
- tenant_idintegerRequired
- scopesarray of stringRequiredWhat the app holds in this project: its consented scopes, never more than the app requests.
- consent_revisionintegerRequired
- rate_limit_per_minuteintegerRequired
- statusenumRequiredOne of
active,revoked - installed_bystringRequired
- installed_atstringRequired
- updated_atstringRequired
- revoked_atstring | nullRequired
- revoked_bystring | nullRequired
- revoked_reasonstring | nullRequireduninstalled or app_archived.
- staff_reasonstring | nullSet when Ivora staff installed the app on the project's request: why. Null for an install by the project's own team.
PATCH /v1/tenants/{tenant_id}/installs/{install_id}
curl --fail-with-body -X PATCH "https://api.ivoracharge.com/v1/tenants/1042/installs/ins_0123456789abcdef0123456789abcdef" \
-H "Authorization: Bearer $IVORA_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'Response · 200JSON
{
"id": "id_0123456789abcdef",
"app_id": "app_0123456789abcdef",
"app_name": "string",
"tenant_id": 1042,
"scopes": [
"string"
],
"consent_revision": 1,
"rate_limit_per_minute": 1,
"status": "active",
"installed_by": "string",
"installed_at": "2026-09-30T17:00:00Z",
"updated_at": "2026-09-30T17:00:00Z",
"revoked_at": "2026-09-30T17:00:00Z",
"revoked_by": "string",
"revoked_reason": "string",
"staff_reason": "string"
}Requires an approved production API keyProduction access starts with a request, a short meeting with Ivora and a card on file, after which Ivora staff grant your account access. How to request access
Try itproduction · api.ivoracharge.com
Paste a production api key (iv_live_…). Create keys in Developer tools. The key stays in this page's memory, is sent only to https://api.ivoracharge.com and clears when you reload. Test keys are refused.
PATCH is a write: you confirm the method, path and project before it is sent, with a generated Idempotency-Key.



