Approve an authorization request
Grants the app the chosen scopes on one project and returns redirect_to, the app's redirect URI with a single-use code, for the browser to open. The scopes must be project scopes you hold on that project. Approving again for the same app and project replaces your earlier grant. Where write scopes need a step-up sign-in, a write scope without a fresh aal2 session is refused with step_up_required. Errors: 403, 403 step_up_required, 404 oauth_request_not_found, 410 oauth_request_expired, 422. See Errors and statuses.
Path parameters
- request_idstringRequired
Request body
- tenant_idintegerRequiredThe project (tenant) the app may act on. One project per grant.Greater than 0
- team_idstring | nullOptional: the project's team, checked when given.Up to 64 characters
- scopesarray of stringRequiredThe scopes granted, within the project scopes you hold. Read-only scopes are the default; write scopes and stations:admin are opt-in.
Returns · 200
any
curl --fail-with-body -X POST "https://api.ivoracharge.com/v1/oauth/requests/request_0123456789abcdef/approve" \
-H "Authorization: Bearer $IVORA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tenant_id": 1042,
"scopes": [
"string"
]
}'nullTry 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.
POST is a write: you confirm the method, path and project before it is sent, with a generated Idempotency-Key.



