One install

GET 
/app_installs/:id

What Manage and Setup read: the install's own facts, its ingest URL, the hourly quota (and whether it is enforced yet), a pending re-consent (only while the install is live), the write rules its grant allows, how many of the partner's agents match active members, and the workspace's working hours — plus why an install reads error (status_reason), the Reconnect its Connected apps row offers, and the legacy credential the install replaced while that still works. An uninstalled install of this workspace stays readable (status: uninstalled); every write refuses it. Another workspace's install, a bigint or junk id is 404. integrations.read. Throttle: app_installs/read/minute, 300 a minute.

A signed-in session or the person's own personal access token; an app's OAuth token is refused (403 resource_not_grantable).

Request

Responses

200

The install.

401

No session or token, or one that is no longer valid. A request that presented a token gets WWW-Authenticate: Bearer realm="KudosCRM", error="invalid_token" (refresh it); one with no credentials and no session cookie gets the bare challenge.

Response Headers

WWW-Authenticate
Example: Bearer realm="KudosCRM", error="invalid_token"

403

Not allowed: the permission this route needs is missing, the Integrations module is off (code: module_disabled, meta.module_key, meta.blocked_at_layer), or the caller is an app's own OAuth token (code: resource_not_grantable).

404

Not found in this workspace — or not something the caller may know exists.