Technical details
API endpoints
| Detail |
Value |
| Per-entity endpoint (Sequence uses this) |
POST /api/v1/sequence/entity/:entityUuid/amount |
| Aggregate endpoint (legacy, still available) |
GET /api/v1/summary/sequence/transfers |
| Auth |
Bearer token (API key generated in IHAB dashboard) |
| Response format |
JSON |
| Amounts |
Integer cents (e.g. 45000 = $450.00) |
| Rate limit |
Standard API rate limiting applied |
| CORS |
Restricted to authorized origins |
Per-entity endpoint — request and response
Sequence POSTs to /api/v1/sequence/entity/:entityUuid/amount with the entity's UUID in the path. IHAB looks up the linked scheduled set-aside and responds:
{
"amountInCents": 45000
}
No body required in the request. The UUID is the lookup key. Authentication is via Bearer token.
Authentication
API keys are generated in your IHAB dashboard under Settings > API Keys. Each key is displayed once at creation — IHAB stores only the SHA-256 hash. Keys can be revoked instantly. You can have multiple active keys.
Aggregate endpoint — response fields
The aggregate GET /api/v1/summary/sequence/transfers endpoint remains available for custom integrations that want a full snapshot in a single call.
| Field |
Type |
Description |
transfers[].name |
string |
Set-aside or allocation name |
transfers[].amount_cents |
integer |
Monthly allocation in cents |
transfers[].priority |
integer |
Priority order (1 = highest) |
transfers[].type |
string |
"savings" or "debt" |
transfers[].target_amount_cents |
integer |
Total target in cents (if set) |
transfers[].target_months |
integer |
Target expressed as months of expenses (if set) |
transfers[].progress_pct |
float |
Percentage toward target |
summary.net_income_cents |
integer |
Net income after taxes |
summary.total_expenses_cents |
integer |
Total recurring expenses |
summary.total_allocated_cents |
integer |
Total allocated to set-asides |
summary.unallocated_cents |
integer |
Remaining unallocated funds |
generated_at |
ISO 8601 |
Timestamp of calculation |
What triggers recalculation
- You change an expense amount or add/remove an expense
- You override a monthly budget amount (without changing your baseline)
- You add, remove, or reprioritize a scheduled set-aside
- A set-aside reaches its target and completes
- A seasonal or non-monthly expense hits the current month
- You update your income amount
Each of these changes is reflected in real time. The next time Sequence calls the IHAB entity endpoint, it gets the updated amount. No manual sync step — IHAB does not push updates to Sequence.
Balance tracking
IHAB reads actual account balances back from Sequence for every linked entity. This gives you planned-vs-actual visibility for every goal and budget category inside IHAB — without needing to connect a bank account directly.
Security
- All API traffic over HTTPS
- API keys hashed with SHA-256 (IHAB never stores plaintext keys)
- Plaid tokens encrypted with AES-256-GCM (bank linking, when available)
- Helmet security headers on all API responses
- Rate limiting on all endpoints
- Firebase Auth (Google SSO) for dashboard access