Float’s API lets you connect Float directly to your existing finance systems. It’s designed to save you time, cut out manual work, and give you real-time visibility into spending.
Full API Documentation is available here: Float API Documentation
What Can You Do with the API?
With our API, you can:
-
Automate your accounting
Access transaction-level data for cards, reimbursements, and payments, as well as account activity like cash back and top-ups. It’s ready to plug into any accounting system. -
Build custom reports
Get real-time access to all Float spend and deposit data. Use this to create dashboards or integrate with your reporting tools. -
Control your chart of accounts
Automatically manage custom fields, GLs, and vendors so Float is always in sync with your ERP.
Who is the Float API for?
-
Tech savvy finance teams or those who have IT teams that automate/integrate systems internally.
If you've built or bought custom integrations in the past, and/or have internal tech or IT resources who support finance workflows today, you're likely ready to use the Float API - You're NOT using Float's built-in NetSuite, QBO, Xero, or accounting integrations
API Tokens
To create and manage API tokens, log in to app.floatfinancial.com as an Administrator and go to Settings > Business Settings > Developers.
Setting Token Permissions
Each API token has its own permissions, so it can access only what your integration needs. For example, a reporting tool can view transactions without being able to create payments.
- Go to Settings > Business Settings > Developers.
- Click Create API Token, or click an existing token's entry in the Permissions column to edit it.
- Under Permissions, choose what the token can do in each group: View, Create, Edit or Delete. A dash means that action isn't available for the group.
- To choose permissions one at a time, expand a group with the arrow beside its name.
- Click Save.
Permissions are grouped by area of Float:
- Accounting: your accounting software connection, and the codes spend is categorized with
- Cards: virtual cards and receipts
- Payments: payments going out, the bills behind them, and who gets paid
- Reimbursements: employee expense claims and reimbursements
- Transactions & Accounts: card and account activity, and account balances
- Users & Teams: people with Float access, and the rules that apply to them
Some important considerations
- Existing tokens keep full access. Tokens created before permissions were introduced have every permission, so your current integrations keep working. Review them and remove anything they don't need.
- Changing data includes viewing it. Giving a token Create, Edit or Delete access also lets it view that data.
- Changes apply immediately. A token's new permissions take effect as soon as you save, with no need to create a new token.
- Who can change permissions: the Administrator who created the token, or the Primary Administrator.
- Tokens are for Administrators only. Permissions limit what a token can do, but only Administrators can create tokens.
- The Permissions column on the Developers page summarizes each token's access at a glance.
Frequently Asked Questions
Can I create a Sandbox environment to test Float's API?
No, Float doesn’t offer a sandbox or test environment for API access.
Can I make an API token read-only?
Yes. When you create or edit the token, click Select all view permissions and leave Create, Edit and Delete unchecked. The token can then read data but can't change anything.