Skip to main content

Answer a version that asks for more

POST 

/app_installs/:id/reconsent

Re-consent happens inside KudosCRM, never through a Kudos-built authorize URL. A release asks an install when the new version requests a scope the install never answered, or requires one it does not hold (one it declined while it was optional included). Until an admin answers, the app keeps its version and grant; its subscription already takes the new version's events, filtered by that grant, and still delivers to the webhook URL the admin agreed to.

allow: the install moves to the pending version with its required scopes plus the optional ones still ticked (optional_scopes[]), the rest declined (and remembered); its subscription and its source follow that version; access tokens are revoked if a scope was removed; the partner's next refresh mints under the new grant. deny: the install stays on its version and grant — its subscription back to exactly that version's events — until a later release asks again. No code, no redirect. Throttle: app_installs/write/minute, 30 a minute.

A cookie session, no impersonation, the CSRF token and an Origin exactly the app's own — 403 cookie_session_required / impersonation_forbidden / invalid_origin. integrations.manage; 422 invalid_decision / not_installed / nothing_pending.

Request​

Responses​

The install.