External Integrations
The QA API integrates with many external services to enable end-to-end test scenarios. This page provides a reference for each integration: its purpose, authentication mechanism, the Go package that wraps it, and which secret (if any) it uses.
Integration Reference
| Integration | Purpose | Auth Mechanism | Go Package / Client | Secret |
|---|---|---|---|---|
Auth0 |
Create user accounts and manage identities |
Management API token |
|
|
Plaid |
Configure bank account overrides and simulation data |
Client ID + secret |
|
|
User Service |
Create and read user profiles (FloatMe internal) |
AWS SigV4 (IAM role) |
|
— |
Float Service |
Create floats, read active float status (FloatMe internal) |
AWS SigV4 (IAM role) |
|
— |
Subscription Service |
Create subscriptions, read subscription status (FloatMe internal) |
AWS SigV4 (IAM role) |
|
— |
LOC Service |
Create loans (Line of Credit) (FloatMe internal) |
AWS SigV4 (IAM role) |
|
— |
Payments Service |
Create payment records for custom user setup (FloatMe internal) |
AWS SigV4 (IAM role) |
|
— |
Underwriting Service |
Read user eligibility status (FloatMe internal) |
AWS SigV4 (IAM role) |
|
— |
Insight Service |
Write income and insight records (FloatMe internal) |
AWS SigV4 (IAM role) |
|
— |
Admin Service |
Perform admin operations (FloatMe internal) |
AWS SigV4 (IAM role) |
|
— |
Transactions Service |
Read bank account transaction data (FloatMe internal) |
AWS SigV4 (IAM role) |
|
— |
Iterable |
Query marketing events and manage user records |
API key (two separate keys: mobile + server) |
|
|
GrowthBook |
Fetch and evaluate feature flags at startup |
SDK key |
|
|
Jira/Xray |
Import |
|
|
— |
DynamoDB |
Query bypass rules table ( |
AWS SigV4 (IAM role) |
|
— |
RDS (PostgreSQL) |
Read float and loan records from the main database |
Password authentication |
|
|
SQS |
Send collection job messages to async processors |
AWS SigV4 (IAM role) |
|
— |
Kinesis |
Inject test events for stream processing |
AWS SigV4 (IAM role) |
|
— |
All secrets stored in AWS Secrets Manager are loaded at Lambda startup via fmsdkSM.BatchGetAndUnmarshalSecrets().
Secrets are referenced by environment variables (e.g., SM_PLAID_NAME) that contain the Secrets Manager secret name. This service is deployed to the test environment only; secret names are configured in the Lambda environment at deploy time.