Instance providers

A Quiddly tenant is modelled as an InstanceProvider (id prefix IP.). Every other entity in the system - clients, debtors, invoices, payments - belongs to exactly one instance provider.

Most Quiddly customers run a single deployment that contains several instance providers - commonly one per country. All instance providers in a deployment share the same API host, and data is visible across them: many resources expose an instanceProviderId you can read and filter on. Some customers instead run one deployment per country, each with a single instance provider and its own host (for example acme-se-api... and acme-fi-api...).

The isolation boundary is the deployment, not the instance provider: data is never visible across hosts, but within a deployment it is visible across instance providers. One instance provider per deployment is marked as the default (GET /instance-providers/default).

Why this matters for the portal

This portal serves this deployment. The interactive reference’s “Try it” button issues requests to {this host}/..., so a successful call here proves your auth works against this deployment - nothing else.