The Moss API gives your organisation direct, programmable access to Moss data. It is typically used by IT teams, data teams, or implementation partners to connect Moss with other systems, automate workflows, and build custom reporting.
This article explains what data is available through the API, how customers use it, what is included, and how to get started.
What data is available?
The API provides access to core data that finance teams work with every day. This includes transactional data, accounting reference data, and organisational data.
Data | Description |
Expenses | All card transactions, invoices, and reimbursements, including line-item detail, amounts, VAT, status, accounting dimensions, and export history |
Suppliers | Supplier names, banking details, default accounting settings, and addresses. You can also create and update suppliers via the API |
Chart of accounts | Your expense account codes and names, as configured in Moss |
Tax rates | All tax rate codes, rates, and country assignments |
Cost centres and dimensions | Your cost centres, cost carriers, and any custom accounting dimensions with their values |
Teams and departments | Your organisational structure as set up in Moss |
Users | Employee names, emails, and roles |
Bank transactions | Money movements in your Moss wallets, including balance movements |
The full list of data models and API reference can be found in the API documentation.
What can you do with the Moss API
Customers use the Moss API to build workflows and reporting that go beyond standard exports. Common use cases fall into four main areas.
Custom financial reporting and cost analysis
Replace manual CSV exports with live dashboards that combine Moss data with other business data.
Pull expense data into Google BigQuery, Looker Studio, or Metabase and give each cost centre owner a self-service P&L drill-down — no more waiting for month-end reports
Connect Moss to your project management system to track profitability across projects by matching expenses to project-level cost centres
Combine expense data with material and resource data to build live views of cash flow, P&L per department, and purchase versus invoices versus payments
How often can the API pull data?
The API supports near-real-time access. Your integration can request updated data as frequently as needed within the published rate limits. Many organisations choose to sync on a schedule, often daily, depending on their requirements
AI-powered expense automation
Connect the Moss API to AI tools like Claude to automate tasks that previously required manual review.
Build a Slack bot that posts daily summaries of credit card transactions and invoices, plus automated budget models
Automate cost classification — detect overlapping SaaS subscriptions, and flag cost outliers
Can I use the API with AI tools?
Yes! You can connect the Moss API to AI tools like Claude to review expenses, generate spend summaries, and detect anomalies.
Multi-entity cash forecasting and reporting
Build a consolidated financial view across all your legal entities.
Create a rolling cash forecast by pulling pending payment data across all entities and visualising it in your BI tool
Analyze your spend across entities with a comprehensive view
System integration
Connect Moss to business systems that don’t have a native Moss integration.
Build sync between Moss and your project management tools — cost centres created in the latter automatically appear in Moss as accounting dimension items
Use the API as the data layer that ties together your full stack — DATEV, BigQuery, Looker, HubSpot, Jira, and more
How to get started
The API is usually used by your IT team or data team. Getting started normally follows four steps.
1. Decide what you need
Start by defining which systems should receive Moss data and what data those systems need. This helps you decide what kind of integration you want to build and which endpoints your team will need to use.
2. Involve your IT team or integration partner
Share your requirements with your IT team, data team, or implementation partner. They should also review the Moss API documentation, which contains the information needed to build the connection.
3. Request API credentials
Your Moss admin can generate API credentials in Moss settings. These credentials are what your IT team will use to connect.
4. Test and go live
Your IT team builds and tests the integration, then enables it for production use.
Security and access control
The Moss API is designed to give your organisation secure, controlled access to your Moss data.
Key security measures include:
Authenticated access only: Every API connection requires secure credentials that are unique to your organisation.
Separate API credentials: API connections use their own credentials, separate from employee login details. No employee passwords are shared.
Rate limits: The API enforces request limits to help prevent misuse and support reliable performance.
Auditable activity: API updates are logged and traceable.
Is data shared with third parties?
No. The API provides access only to your own organisation’s data, only to applications you explicitly authorise with your credentials. Moss does not share your data with any third party through the API.