Controls
API keys, usage & webhooks
Integrate through scoped credentials and inspect technical activity.
Workflow
What you can do with API keys, usage & webhooks.
The page, action and status model stays clear from the first step to the final record.
Create scoped credentials
Choose the company authority the key is allowed to exercise.
Use idempotent operations
Retry safely without duplicating records or money instructions.
Verify webhooks and usage
Sign events and show when and how credentials were used.
Visible lifecycle
Know what happened, what is waiting and who owns the next step.
Kua keeps the working record, status and responsible person together so a user does not have to infer progress from a notification or bank balance.
Ready to begin
The page shows the prerequisites, authority and information needed before submission.
Waiting for review
The current reviewer, submitted version and requested changes remain visible.
Completed with evidence
The final outcome, timestamps and connected records remain reachable to authorised users.
Controls
What keeps the feature trustworthy.
Availability and authority are evaluated before an action is offered, and the server enforces the same rule.
ManageRoles authority
Kua applies manageroles authority to this capability and keeps the resulting status visible.
Secret shown once
Kua applies secret shown once to this capability and keeps the resulting status visible.
Rotation and revocation
Kua applies rotation and revocation to this capability and keeps the resulting status visible.
Use api keys, usage & webhooks as part of one connected system.
Explore the related product or talk to Kua about your organisation and country.