Core Concepts
Link to this section#Environments
An Environment serves as an isolated container for your Profiles and associated data. Each Environment has its own Integrations and you can have as many Environments as your use-case requires. There are three Environment modes:
| Mode | Billable | Description |
|---|---|---|
SANDBOX | No | Unlimited mock operations, suitable for local development and automated testing. |
DEVELOPMENT | No | Limited live operations, suitable for staging and QA use-cases. |
PRODUCTION | Yes | Unlimited live operations, suitable for production use. |
Link to this section#Profiles
A Profile represents an individual end-user associated with an Environment. In addition to financial data each Profile can contain additional information such as email, phone, name, birthday, address and more. These fields can be used to allow end-users to authenticate with the Quiltt Connector, or for compliance requirements mandated by one of your integrations, such as KYC.
You can request ephemeral Session tokens to access the Profile GraphQL API and the Quiltt Connector for a given Profile.
While all customer data is encrypted at rest, Quiltt automatically applies additional column-level encryption to sensitive Profile fields that may contain PII.
Link to this section#API Keys
An API Key allows you to programmatically interact with a Quiltt Environment. Each Environment will typically be provisioned with one or more API Keys, depending on your use-case.
Each API Key has a secret which can be used to authenticate to the Auth API and the Admin API.
Link to this section#Integrations
An Integration represents a 3rd party provider configuration in a given Environment. This include services like Plaid, MX, Spade and others.
Integrations can be managed in the Dashboard and be configured to use your own API credentials or credentials provided by Quiltt.