Request a capability
Ask for one of your sub-clients to be enabled for a capability, and get back the link where the sub-client answers its requirements. How a request is decided says what happens next.
Calling it again for the same sub-client and capability is safe. While the request still waits on the sub-client, you get the same request back with 200, and with a fresh verification_link once the earlier one has expired.
Authorizations
The data.access_token value from Get access token.
Headers
Version applied to this request. It wins over your account's pinned version — see Versioning.
"2026-04-14"
Body
Response
The sub-client already had a request open for this capability, still waiting on it. This is that request, with a link that has not expired.
A request that a sub-client be enabled for a capability — see The capability request object.
The request's identifier.
The sub-client the request is for.
Identifies the list of requirements the request was opened against. It changes when that list changes.
The link where the sub-client answers the requirements.
Only while status is requested.
When verification_link stops working, ISO 8601. Request the capability again with Request a capability for a fresh link.
What the sub-client sent, once Kira has kept a copy of it. The answers and files themselves are never returned.
The latest review outcome. Absent until compliance has reviewed the request.
The capability the approval granted. Only on an approved request.
When the request was opened, ISO 8601.
When the sub-client sent its answers, ISO 8601. null until then.
When the request was approved or rejected, ISO 8601. null until then.