Flinq integration access

Use the integration route that matches the approved task, authentication method and data exchange required by your organisation.

Choose an integration route

• REST API: use a permission-scoped API token for an approved system-to-system integration and supported Flinq operation.

• Importer or exporter: use a configured banking-data connection for statement intake or Interest Pooling payment instructions.

These routes are separate. A credential for one route does not grant access through another.

REST API access

API access combines the token's selected scopes with the current user's office and record access. Supported operations can include reading permitted banking, reporting or Interest Pooling records and uploading statements. Optional-product operations appear only when the related product and API surface are available.

An API token does not enable a product, add office access or override record permissions. Confirm the approved API operation and response contract with the integration owner before development.

Banking-data connections

Importers convert supported statement data into Flinq records. Exporters create or send supported Interest Pooling payment instructions. Manual, automated and managed connection options depend on the bank, format, deployment and operating model; the presence of a connector does not confirm that it is active for an office.

Before go-live

• Use a separate credential for each integration.

• Grant the minimum scopes, office access and product permissions required.

• Store secrets in an approved secret manager and agree a rotation and revocation process.

• Test with representative non-production data and confirm the expected audit evidence.

• Document the owner, approved route, supported operations and recovery contact.

Next steps

For REST API credentials, see How to manage API tokens. For banking-data connections, see How to configure an importer and How to configure an exporter.