Skip to main content
The client is your business — the one with the agreement with Kira, the credentials, and the accountability for everything done through them. There is exactly one client per integration, and it is not something you create through the API. Kira sets it up when the relationship starts and hands you the credentials that identify it.

​
What belongs to a client

Everything else in the model hangs off the client. Your sub-clients, their accounts, the counterparties you pay and every transfer you make all belong to one client, and nothing crosses between clients. That boundary is why your data is only ever your data: a call made with your credentials can only see and touch what belongs to you.

​
What a client decides

  • Who your sub-clients are — you onboard them, Kira verifies them.
  • What each movement is for — Kira carries it out and records it; it does not decide the purpose.
  • What your customers experience — Kira is underneath your product, not beside it.

​
What it is called elsewhere

The client is not a resource you read or write, so it has no page in the API reference. It is the thing your credentials stand for: every authenticated call is made as your client, which is why nothing you send has to say who you are.
A client is you. A sub-client is one of your customers. The two are easy to confuse in conversation and never in the data — see Sub-client.