Skip to main content
A capability request asks Kira to enable one of your sub-clients for something beyond its verification, such as paying on behalf of its own customers. The sub-client answers the capability’s requirements through a link, and compliance reviews the answers. A sub-client has at most one open request per capability.

Example

Fields

The fields that only apply at some stages are left out of the response, not sent as null.

How a request is decided

  1. Request a capability for a verified business sub-client. The request opens as requested, with a verification_link.
  2. Send the sub-client to verification_link. The link lasts 30 days. Once it has expired, request the capability again: you get the same request back with a fresh link.
  3. When the sub-client sends its answers, the request moves to submitted and compliance reviews it. Compliance may also open a request for information about it.
  4. The review ends one of three ways:
    • Approved. status becomes approved and grant.status is granted. The sub-client can use the capability.
    • Sent back. status returns to requested with review.reject_type RETRY and a new verification_link. The sub-client completes what was missing and sends it again.
    • Rejected. status becomes rejected with review.reject_type FINAL. You cannot request that capability for the sub-client again.
No webhook reports these moves. Read status with Get a capability request, or many sub-clients at once with List capability requests and latest=true. A granted capability can be revoked later. grant.status then reads revoked, and the sub-client can no longer use it or request it again.