Environments
The flinkey platform provides two separate environments. Every new integration must start on UAT and pass validation before production access is granted.
UAT (User Acceptance Testing)
Section titled “UAT (User Acceptance Testing)”The UAT environment is your development and testing playground.
| Resource | URL |
|---|---|
| API Base URL | https://api-uat.flinkey.de/v3 |
| flinkey Portal | portal-uat.flinkey.com |
PROD (Production)
Section titled “PROD (Production)”The production environment serves live data.
| Resource | URL |
|---|---|
| API Base URL | https://api.flinkey.de/v3 |
| flinkey Portal | portal.flinkey.com |
Environment-specific configuration
Section titled “Environment-specific configuration”Each environment has its own set of credentials and configuration values. These must never be mixed.
| Parameter | UAT | PROD |
|---|---|---|
| API Base URL | https://api-uat.flinkey.de/v3 |
https://api.flinkey.de/v3 |
| flinkey Portal | portal-uat.flinkey.com | portal.flinkey.com |
| Customer-ID | UAT-specific | PROD-specific |
| flinkey-API-Key | UAT-specific | PROD-specific |
| API Manager credentials | UAT-specific | PROD-specific |
| Webhook URL + Secret | UAT-specific | PROD-specific |
| SDK Key | UAT-specific | PROD-specific |
See Portal & Credentials for details on how to configure these values using environment variables.
Key differences
Section titled “Key differences”- UAT may contain test data and can be reset during onboarding.
- Production credentials are only issued after successful validation of your integration on UAT.
- Both environments use the same API contract (
openapi.json), but operate on separate databases and separate credentials.
Validation process
Section titled “Validation process”After developing on UAT, the flinkey team reviews your integration. Once approved, your production API key is issued through the flinkey Portal (PROD).