Resources
Known limitations
What v1 doesn't do yet, and how to work around it. When one of these changes, the changelog says so.
| Limitation | What it means | Workaround |
|---|---|---|
| No service catalogue endpoint | You can't list services or their ids through the API. | The organization admin gives you the serviceIds for invoice lines. |
| No bank account endpoint | You can't list the ids for defaultSettlementBankId. | The organization admin gives you the ids, if you need them. |
| Enrollments lack the billing cycle | GET /customers/{id}/enrollments doesn't return billingCycle or nextBillingDate. | The enrollment webhook object has both. |
| No enrollment changes | Enrollments are read-only in the API. | They're managed in the Flux app. |
| No invoice changes | The API can't update, approve, return or void invoices. This is by design: approval is a human control. | People do it in the Flux app; you hear by webhook. |
| Contacts missing from lists | List results return contacts: null. | Get the customer by id. |
| Timestamps without an offset | Most object timestamps have no time zone offset. | See Dates and timestamps. |
| No sandbox or test keys | Every key is a live flx_live_ key. | Develop against a staging organization. |
| No “changed since” filter | Lists can't be filtered by update time. | Use webhooks, and read individual objects to reconcile. |