Smartbooks API × AmbactiBring Smartbooks API into
the flow of work.
A little less busywork with Smartbooks API.
Input1 capabilities+
- Batch input
Batch input for a given year and period. Requires scope input:write.
Module2 capabilities+
- Get module
Get a module by code. Requires scope modeling:read.
- Add account
Add an account to a subaccounts table of a module. Requires scope modeling:write.
Reporting3 capabilities+
- Get outstanding payables
Get outstanding payables. Requires scope reporting:read.
- Get outstanding receivables
Get outstanding receivables. Requires scope reporting:read.
- Get yearly amounts
Get yearly amounts for a given year. Requires scope reporting:read.
Structure4 capabilities+
- Get balance sheet structure
Get balance sheet structure. Requires scope reporting:read.
- Get cash flow structure
Get cash flow structure. Requires scope reporting:read.
- Get metrics structure
Get metrics structure. Requires scope reporting:read.
- Get profit and loss structure
Get profit and loss structure. Requires scope reporting:read.
Profile1 capabilities+
- Get profile
Get profile details including allowed tenants and companies. Requires scope profile:read.
Frequently asked
questions.
What could an Ambacti integration do with Smartbooks API?
The documented operations include Input: Batch input; Module: Get module; Module: Add account; Reporting: Get outstanding payables.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in Smartbooks API?
Decide which work could run on its own and which steps need your review.