BTCMatic × AmbactiBring BTCMatic into
the flow of work.
A little less busywork with BTCMatic.
Rule8 capabilities+
- Create a rule
Create a rule. Order rules created via API key always start in dry-run mode.
- Delete a rule
Permanently delete a rule
- Disable a rule
Pause a rule (legal from any state)
- Enable a rule
Resume a disabled rule
- Get a rule
Get a single rule
- Get many rules
List all rules
- Reactivate a rule
Clear a suspended state (e.g. after fixing exchange keys)
- Update a rule
Replace a rule document (full PUT)
Fire1 capabilities+
- Get many fires
List rule fires with their evaluation traces, newest first
Order1 capabilities+
- Get many orders
List orders (live and simulated), newest first
Backtest2 capabilities+
- Create a backtest
Queue a backtest run (returns immediately; poll with Get)
- Get a backtest
Get backtest status and report
Inbound Hook4 capabilities+
- Create an inbound hook
Create an inbound hook. The delivery path and signing secret are returned exactly once — store them.
- Delete an inbound hook
Revoke an inbound hook (deliveries 404 afterwards)
- Get many inbound hooks
List inbound hooks (tokens and secrets are never returned)
- Send an event to an inbound hook
Post an event to an inbound hook so webhook-triggered BTCMatic rules can evaluate it
Frequently asked
questions.
What could an Ambacti integration do with BTCMatic?
The documented operations include Rule: Create a rule; Rule: Delete a rule; Rule: Disable a rule; Rule: Enable a rule.
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 BTCMatic?
Decide which work could run on its own and which steps need your review.