Fyle API
Fyle (now Sage Expense Management) is an AI-powered expense management platform that automates receipt capture, expense reports, corporate card reconciliation, approvals, and ACH reimbursements for SMBs. An API lets you programmatically pull expenses, reports, receipts, card transactions, mileage, per-diems, and approval status—and push updates like new expenses, report submissions, and approvals back into Fyle, then sync to QuickBooks, NetSuite, Sage Intacct, Sage 300, and Xero.
What is Fyle?
Fyle (now Sage Expense Management) is an AI-powered expense management platform that automates business expense tracking, receipt collection, and corporate card reconciliation for small and mid-sized businesses. Employees submit receipts by text, email, Slack, or the mobile app; Fyle extracts the data in real time, codes expenses to the general ledger, enforces policy, routes approvals, and reimburses employees via ACH—then syncs the results into accounting systems.
Core product areas include:
- Expense automation (Text-to-Expense, receipt capture, real-time data extraction, AI GL coding)
- Expense workflows (automated approvals and routing, policy compliance checks, employee reimbursements via ACH)
- Card management (Visa, Mastercard, and American Express reconciliation, real-time card feeds, virtual card issuance)
- Spend insights (budget configuration and tracking, real-time reporting, compliance monitoring)
- Mileage and per-diem tracking, multi-entity and multi-currency support, and the Copilot AI assistant
Common data entities:
- Expenses, Receipts, Categories, Custom Fields
- Reports, Approvals, Approval Chains, Policy Violations
- Corporate Card Transactions, Card Feeds, Virtual Cards
- Reimbursements, Payments, ACH Batches
- Mileage, Per-Diem Rates, Budgets, Projects, Cost Centers
- Employees, Spenders, Admins, Departments, Org Settings
The Fyle Integration Challenge
Fyle publishes a REST API, but turning a mobile-first, approval-driven expense workflow into reliable automation across a customer's org still presents hurdles:
- OAuth and token lifecycle: API access is gated behind OAuth with refresh tokens, and credentials must be provisioned and rotated per org
- Spender vs. Admin scopes: endpoints split across Spender and Admin APIs, so the same entity is reachable through different surfaces depending on role and entitlements
- Mobile-first data: much expense and receipt capture happens through the mobile app and Text-to-Expense, so data lands asynchronously and out of order
- Rate limits and pagination: large expense and card-transaction volumes require careful cursor pagination and throttling to avoid hitting limits
- Approval and policy state: report submission, approval routing, and policy-violation flags are stateful and must be read and written in the right lifecycle order
- Accounting sync coupling: expenses are continuously exported to QuickBooks, NetSuite, Sage Intacct, and Xero, so field mappings and custom fields vary per customer
How Supergood Creates Fyle APIs
Supergood combines Fyle's published Spender and Admin REST APIs with authenticated session flows to deliver a single, resilient API layer for your Fyle org—handling OAuth, pagination, and lifecycle state so you integrate once.
- Handles OAuth credentials, refresh tokens, and MFA securely in a managed session
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across Spender and Admin APIs so expenses, reports, cards, and approvals expose consistent objects
- Aligns with org-specific categories, custom fields, projects, and accounting mappings to keep exports compliant
Use Fyle with AI agents: Fyle MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your Fyle modules, accounting integrations, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Fyle adapter tailored to your org's Spender/Admin scopes and custom fields.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Fyle evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Fyle org via OAuth and obtain a session token for downstream Spender and Admin calls.
Expenses
/expensesList expenses with filters for state, date range, category, project, card transaction, and policy-violation status.
Expenses
/create_expenseCreate an expense with merchant, amount, category, project, and receipt attachment on behalf of a spender.
Reports
/reportsRetrieve expense reports with approval state, approver, submitted/paid status, and line-item details.
Reports
/submit_reportBundle expenses into a report and submit it into the approval workflow for routing.
Cards
/card_transactionsPull corporate card transactions and feeds across Visa, Mastercard, and American Express for reconciliation.
Use Cases
Sync expenses and reports into your warehouse
- Pull expenses, receipts, and report state from Spender and Admin APIs into a single warehouse - Stream approval and policy-violation events to downstream finance and BI tools - Reconcile expense, project, and cost-center records for unified spend reporting
Automate corporate card reconciliation
- Pull card transactions and feeds across Visa, Mastercard, and American Express - Match transactions to expenses and flag unreconciled or out-of-policy charges - Push matched card data and GL codes back for accounting export
Drive approvals and reimbursements programmatically
- Submit reports into approval chains and read routing and approver status without portal clicks - Trigger ACH reimbursement batches once reports are approved and paid - Surface delinquent approvals and policy violations to finance workflows
Keep accounting systems in sync
- Export coded expenses to QuickBooks, NetSuite, Sage Intacct, Sage 300, and Xero - Map org-specific categories, custom fields, and projects to GL accounts - Pull mileage, per-diem, and budget data for reporting and reconciliation
Technical Specifications
Authentication
OAuth 2.0 with refresh tokens and MFA handled in a managed session
Connectivity
Fyle Spender and Admin REST APIs plus authenticated browser flows where endpoints are not exposed
Response format
Normalized JSON across Expenses, Reports, Cards, Approvals, and Reimbursement objects
Rate limits
Adaptive throttling and cursor pagination tuned to your org to avoid Fyle-side limits
Session management
Automatic OAuth token refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for expenses, card feeds, and approvals with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for expense creation, report submission, approval, and reimbursement status
Latency
Sub-second reads on cached entities; multi-second writes when submitting reports and reimbursement batches
Throughput
Horizontally scaled workers sized to high-volume expense and card-transaction loads
Reliability
Retry, backoff, and idempotency keys for expense creation, report submission, and payments
Adaptation
Continuous monitoring of Fyle API releases and org-specific category and custom-field drift
Frequently asked questions
Yes. Supergood normalizes data across Fyle's Spender and Admin APIs, so you can read and write expenses, reports, cards, and approvals through one consistent surface regardless of which role exposes them.
Yes. Card transactions and feeds across Visa, Mastercard, and American Express are exposed as normalized objects, so you can match them to expenses, flag exceptions, and push GL codes for accounting export.
Report submission, approval routing, and ACH reimbursement status are stateful operations Supergood handles in the correct lifecycle order, so you can submit reports and trigger reimbursements programmatically.
Yes. Supergood preserves your org-specific categories, custom fields, and projects so coded expenses continue to export cleanly to QuickBooks, NetSuite, Sage Intacct, Sage 300, and Xero.
No. Fyle now operates as Sage Expense Management, but the underlying API surface, OAuth model, and data entities remain the same, and Supergood adapts automatically as the platform evolves.