Getting Started
This page explains what you need before calling the Onboarding API: environments, authentication, the fields that appear in every request and how to read responses.
Environments
Fits provides a sandbox environment for tests and a production environment. Use the sandbox to validate your integration before going live. Test data in the sandbox must be fictitious.
Authentication
Requests are authenticated with Basic Auth or, optionally, with mTLS. See Authentication and Authentication via mTLS. Keep credentials outside your source code and never share them in tickets, chats or logs.
Fields present in every request
| Field | Meaning |
|---|---|
| Method | Name of the operation being called |
| PartnerId | Identifier issued by Fits for your integration |
| BusinessUnitId | Identifier of your Business Unit (BU) |
Reading responses
Responses return Success and Message. The Success field comes as text ("true" or "false"), not as a boolean.
In operations that are completed later, such as account opening, Success "true" means the request was accepted for processing. It does not mean the registration was approved: the final result of the analysis arrives through webhooks and queries. In other methods, Success "true" indicates that the operation was completed, as in account blocking and rate changes. In the request for a new Protege+ check (UnlockAccount with justification 6), the initial response does not confirm the unlock. Success "true" also does not guarantee data in the response: a query can return success with empty lists, such as GetSigners when there are no signers. Error messages are in the Error Catalogue and success messages in the Success Catalogue.
Updated 11 days ago

