Resources and inventory
- /api/v1/resources
- /api/v1/resources/summary
- /api/v1/resources/insights
- /api/v1/resources/scheduling-policy
Automation
API and Automation
TurboFinOps supports API-first integration for inventory, savings signals, approved actions, receipts and audit evidence.
Savings signals and findings
- /api/v1/findings
- /api/v1/findings/savings-summary
- /api/v1/findings/scorecard
- /api/v1/findings/trend
Actions and readiness
- /api/v1/actions
- /api/v1/actions/catalog
- /api/v1/actions/readiness
- /api/v1/actions/validation-report
Receipts, audit and exports
- /api/v1/savings/ledger
- /api/v1/audit/logs
- /api/v1/audit/evidence
- /api/v1/audit/exports/*
Automation Notes
Use tenant-scoped authentication on every API call.
Preserve correlation IDs in automation clients for traceability.
Use idempotency keys for state-changing action endpoints.
Prefer dashboard proxy routes for browser-based operations.
Common Automation Playbooks
Daily savings digest
- Call savings summary and trend endpoints every morning.
- Highlight new high-confidence actions above a chosen monthly threshold.
- Post digest into Slack or Teams with owner assignment links.
Approval queue sync
- Poll action requests in pending approval state.
- Mirror approval decisions into Jira or ServiceNow tickets.
- Write back ticket IDs so evidence stays linked to execution.
Receipt checkpoint monitor
- Read verified savings states for pending and verification windows.
- Notify owners at 7, 14, and 30 day checkpoints.
- Escalate regressed receipts for rollback or follow-up actions.
Conversion Event Validation
Use this checklist to validate marketing event ingestion and A/B experiment measurement after deployment.
- Enable `NEXT_PUBLIC_MARKETING_EVENTS_DEBUG=true` in staging during validation.
- Open homepage and confirm `experiment_assignment` and `experiment_impression` fire once per session.
- Click hero and bottom primary CTAs; confirm `primary_cta_click` with experiment metadata.
- Verify payload fields in vendor dashboard: `tfo_event`, `tfo_location`, `tfo_experiment_name`, `tfo_experiment_variant`.
- Compare impression-to-click ratios by variant before making CTA decisions.
Open Analytics Validation to emit test events and confirm destination detection before checking vendor dashboards.
API responses use typed wrappers with data, meta and error fields. Do not rely on raw provider errors or unscoped tenant context.
Get started
Find recoverable spend before the next invoice lands.
Connect one AWS, Azure or GCP scope, approve the safest savings actions, and give finance a receipt when the savings verify.
Read-only scan first. Approval gates before remediation.