Your admin costs you hours every week. Entering invoices by hand, matching bank transactions, syncing customer data between systems. Sound familiar? With a Moneybird developer integration you automate these processes completely. From automatic invoicing to real-time financial dashboards, the Moneybird API offers endless possibilities for smaller businesses that want to grow without administrative baggage.
At Green Creatives we have been building Moneybird integrations for years for e-commerce companies, SaaS platforms and financial service providers. In this article we share everything you need to know about Moneybird developer accounts, the API, OAuth authentication and the newest MCP integrations for AI-driven automation.
What is a Moneybird developer account?
A Moneybird developer account gives you access to the Moneybird API, which lets you connect external applications to your accounting software. That account is essential for anyone who wants to build custom integrations, whether you are a software developer yourself or you bring in an agency to build the connections.
No Moneybird account yet? To get started with the API you obviously need a Moneybird account first. Not working with Moneybird yet? Try it for free via moneybird.nl and find out why thousands of business owners run their bookkeeping with it.
With a developer account you get:
API access: full access to all Moneybird endpoints for contacts, invoices, payments, projects and more
Sandbox environment: a test administration where you can safely experiment without touching real data
OAuth credentials: client ID and client secret for secure authentication
Webhook configuration: automatic notifications whenever something changes in the administration
You create a developer account from your Moneybird user account under Settings → Developers. Once you have filled in the form you get access to your API credentials and you can start building right away.
Why choose a custom Moneybird integration?
Moneybird already offers standard connections with popular tools such as Zapier, Mollie and various banks. Even so, more and more companies choose a bespoke integration. The reasons are clear.
Limitations of standard connections
Standard connections are designed for the masses. They cover the basics, but they fall short on specific business processes. A webshop selling products with variable VAT rates, seasonal discounts and complex returns handling quickly runs into the limits.
Advantages of a bespoke build
A custom Moneybird integration adapts to the way you work, not the other way around. You decide exactly which data gets synced, when invoices are generated and how exceptions are handled. The result is less manual work, fewer mistakes and an administration that is always up to date.
How much time you save depends on your current situation, but clients who move from manual entry to automated workflows structurally save hours per week on administrative tasks. Combined with AI-driven automation you can push that gain even further.
8 popular Moneybird integrations
Based on what the Moneybird API can do and our experience with smaller business clients in e-commerce, SaaS and the financial sector, these are the integration scenarios that come up most often.
1. Automatic invoicing
This is by far the most requested integration. Companies want invoices generated automatically from a trigger: a completed project, products sold, hours delivered or a subscription period that has run out.
A consultant who works by the hour logs those hours in Clockify or Asana. At the end of the month draft invoices are generated automatically, based on logged hours, hourly rates per client and project codes. No manual entry, no forgotten invoices.
2. E-commerce integrations
Webshops on WooCommerce, Shopify, Magento or Lightspeed want orders to land in Moneybird as invoices automatically. Including the right VAT rates, product descriptions and customer details. Often combined with stock syncing and returns handling.
The integration makes sure every order shows up in your bookkeeping as an invoice within minutes, posted correctly to the right ledger accounts.
3. CRM syncing
Keeping contact details in sync between Moneybird and systems such as HubSpot, Pipedrive, Salesforce or your own customer database. New client in the CRM? A contact is created in Moneybird automatically. Invoice history flows back into the CRM for sales insight.
That prevents double entry and makes sure your sales team always has current financial data to hand during client conversations.
4. Time tracking and project management
Integrations with tools such as Teamleader, Simplicate, Asana, Monday or Clockify. Hours worked turned straight into billable lines. Especially popular with agencies, consultants and freelancers who work by the hour.
5. Subscription management and recurring billing
SaaS companies and service providers with monthly contracts want automatic recurring invoicing. Often linked to their own customer portal or to a payment platform such as Mollie or Stripe.
A SaaS platform sends monthly invoices to every active customer automatically, with the correct tiered prices and any overage charges.
6. Bank account syncing and reconciliation
Matching bank transactions to outstanding invoices automatically. That cuts down manual bookkeeping and keeps the administration current. Moneybird already offers standard functionality for this, but custom logic makes it even more powerful.
7. Quote to invoice workflows
Generating quotes from a CRM or a configurator, having the client approve them, and turning them into an invoice and a project automatically once they agree. A streamlined flow in which quotes are generated from an intake form, can be signed digitally, and after approval are converted automatically into projects and invoices in Moneybird.
8. Reporting and BI dashboards
Pulling data out of Moneybird into Power BI, Google Data Studio or your own dashboard for financial reporting and KPI tracking. Real-time insight into revenue, outstanding invoices, cash flow and payment behaviour.
How does the Moneybird API work?
The Moneybird API is a RESTful interface that makes communication possible between external applications and your Moneybird administration. You can create contacts, generate invoices, register payments and pull financial reports.
Authentication: OAuth 2.0 and personal access tokens
Moneybird supports two authentication methods.
OAuth 2.0 is the method of choice for applications that need access to an administration on behalf of a user. That is what you use for SaaS products or multi-tenant solutions.
Personal access tokens are ideal for internal integrations where you only need access to your own administration. Faster to implement, but less flexible.
Available endpoints
The API offers endpoints for almost everything Moneybird does:
Contacts: creating, updating, retrieving and filtering customer and supplier details
Sales invoices: generating, sending and following up invoices
Purchase invoices: registering incoming invoices
Financial accounts: access to ledger accounts and financial data
Payments: registering and matching payments
Projects: managing projects and time tracking
Reporting: pulling the profit and loss statement, balance sheet and cash flow analyses
Rate limits
Moneybird applies a limit of 150 requests per 5 minutes per administration. That sounds generous, but with bulk operations or several users on the same administration you hit it quickly.
Every response comes with headers that tell you how many requests you have left: X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. A well built integration takes those into account and implements queuing with exponential backoff.
Moneybird OAuth: authentication step by step
OAuth authentication is often the stumbling block for developers working with the Moneybird API for the first time. Here are the most common traps and how to avoid them.
Token expiry and refresh handling
Moneybird access tokens expire after a certain time. Plenty of developers forget to build a solid refresh mechanism. Your application has to fetch a new access token with the refresh token automatically before the current one expires, without the user having to log in again.
Solution: build token refresh middleware that checks on every API call whether the token is about to expire and, if so, refreshes it first. Store the access token, the refresh token and the expiry timestamp securely.
Support for multiple administrations
One Moneybird account can have access to several administrations. After OAuth you get a list of administrations and the user has to choose which one gets connected. Developers often fail to build this in properly, which means data ends up in the wrong administration.
Solution: pull the administrations straight after authentication via /administrations and make the user select one explicitly. Store the chosen administration_id and use it on every subsequent call.
Scope limitations
You have to request the right scopes up front. Ask for too few and you get 403 errors on certain endpoints. Ask for too many and you scare the user off at the authorisation screen.
Solution: work out in advance which endpoints you need and request only the minimum scopes required. Document that clearly for the user.
Callback URL configuration
The redirect URI has to match exactly what is configured in Moneybird, including trailing slashes and http versus https. Small deviations produce cryptic errors.
Solution: always use HTTPS in production. Test the exact callback URL and avoid dynamic parameters in the path.
Moneybird MCP: AI integration for smarter bookkeeping
Moneybird recently launched MCP (Model Context Protocol) support. That opens the door to AI-driven automation of your administration.
What is MCP?
MCP is a protocol that connects AI assistants such as Claude to external applications. Instead of looking up or entering data by hand, an AI assistant can communicate directly with your Moneybird administration.
Available MCP servers for Moneybird
There are currently three options for Moneybird MCP integration:
Vanderheijden86 Moneybird MCP Server (open source)
The most complete open-source option, written in TypeScript with full type safety through Zod schema validation. Available tools:
Contact management: retrieving, filtering, creating and updating contacts with advanced filter options
Financial data access: viewing sales invoices, financial accounts and payments
Business operations: managing products, projects and time tracking
Custom API requests: making your own requests to Moneybird endpoints
Advanced contact filtering with query syntax such as
created_after:2023-01-01
Zapier MCP for Moneybird
Handy if clients are already inside the Zapier ecosystem. Offers real-time action automation and task management.
Composio MCP integration
Connects Moneybird to AI agents through MCP. Supports integration with Claude, Cursor, Windsurf and other AI applications. Offers 21+ tools for accounting automation.
Practical AI applications
With MCP you can put AI assistants to work for:
Natural language queries: "which invoices from client X are still open?"
Automatic categorisation of transactions based on patterns
Proactive insights: "your revenue from service Y has dropped 30% compared with last quarter"
Automated reporting in plain language
Want to know more about AI implementations for your business? Have a look at our AI agent services for bespoke solutions.
Webhooks: real-time syncing
Webhooks are the most efficient way to stay on top of changes in Moneybird without polling constantly.
Configuration
Configure webhooks through the API or by hand in Moneybird under Settings → Developers → Webhooks. Pick only the events you actually need, to keep the noise down.
Best practices for webhook handling
Fast response: your webhook endpoint has to respond quickly, ideally within 3 seconds. Receive the webhook, drop it in a queue and return a 200 immediately. Process the payload asynchronously.
Idempotency: webhooks can be sent twice. Every webhook has a unique ID in the payload. Check in your database whether that ID has already been processed before you act on it.
Validation: verify that the webhook really does come from Moneybird. Check the sender IP against Moneybird's known ranges, or implement a shared secret in the webhook URL.
Failure handling: if your endpoint fails, Moneybird tries again at increasing intervals. Make sure your endpoint is idempotent so retries cause no problems.
How long does a Moneybird integration take?
The lead time for a Moneybird integration depends on the complexity and on your specific requirements. Below is an indication based on our project experience:
Phase | Indicative lead time |
|---|---|
Intake and needs analysis | 1-2 hours |
Client creates a developer account | Same day (on their own, with an instruction video) |
API credentials and OAuth setup | 1-2 days |
Building and configuring the integration | 2-5 days (depending on complexity) |
Testing with client data | 1-2 days |
Go live and aftercare | 1 day |
Indication: 1-2 weeks for a standard integration. More complex integrations with bespoke work can take 3-4 weeks. These timelines are indicative and can vary depending on your specific situation.
Frequently asked questions about Moneybird integrations
These are the questions we get most often from clients.
Beforehand
"Is my data safe? Who has access?"
Moneybird uses OAuth 2.0 for authentication. That means your password is never shared with external applications. You give explicit permission for specific scopes and you can always withdraw that permission. Data is sent encrypted over HTTPS.
"What does it cost if something goes wrong or changes?"
A well built integration has monitoring baked in. You get notifications when something fails and you can fix problems quickly. Changes to Moneybird's API are announced well in advance through their developer newsletter.
"Does this work with multiple administrations as well?"
Yes. A properly built OAuth flow lets the user choose which administration gets connected. You can also connect several administrations to the same application.
During setup
"Where do I find my API token and administration ID?"
Go to User account → Developers for your API token. You will find your administration ID in the URL of your Moneybird administration or through the /administrations endpoint.
"Do I have to change anything in my Moneybird settings?"
For most integrations, no. You do have to authorise the external application through OAuth. For webhook integrations you configure the webhook URL in the settings.
"Can I test this first without creating real invoices?"
Yes, Moneybird offers a sandbox environment. Create it through User account → Developers → Sandbox administration. There you can experiment safely with test data.
After going live
"Why has invoice X not been synced?"
Check your integration's logs first. It is usually a validation error, for example a missing VAT number or an invalid amount. Good integrations log every error with enough context to diagnose the problem.
"Can I pause the integration temporarily?"
Yes, you can withdraw the OAuth authorisation in Moneybird under Settings → External applications. The integration then stops immediately. Reactivating it means logging in and authorising again.
"How do I add a new field or a new workflow?"
That takes a change to the integration. Depending on the complexity it can be anything from a few hours to a few days of work. An integration built in modules is easier to extend.
Why Green Creatives for your Moneybird integration?
At Green Creatives we go further than just building an integration. We are an AI agency that combines automation with artificial intelligence. For us a Moneybird integration is often the starting point of a much broader transformation.
More than bookkeeping alone
Where other parties stop at the API integration, we look at the whole picture. How does data flow through your organisation? Where are the bottlenecks? Which processes can you automate further?
A Moneybird integration gets more powerful when you combine it with:
AI-driven receivables management that sends personalised reminders automatically
Financial dashboards with predictive analysis
Client portals where clients look up their own invoice history
Quote to invoice flows with digital signatures
How we work
We guide clients with a thorough intake, clear process descriptions and explainer videos. You know exactly which steps to take and what you can expect from us.
Our aim is to have your entire bookkeeping run hand in hand with Moneybird. Not only day to day invoicing, but your VAT returns, your year-end close and your financial reporting too.
Getting started with your Moneybird integration
Ready to automate your admin? Do you not have a Moneybird account yet? Start for free today via moneybird.nl and see for yourself how intuitive online bookkeeping can be.
Already working with Moneybird and want an integration built? The first step is simple: get in touch for a no-obligation conversation. We look at your current situation, talk through the options and give you a realistic estimate of cost and lead time.
No strings attached, just concrete insights you can put to use straight away, even if you decide to do it yourself or to bring in another party.
Frequently asked questions about the Moneybird API token limit
What is the Moneybird API token limit?
Moneybird applies a rate limit of 150 requests per 30 seconds per API token. As soon as you hit that limit, the API returns a 429 Too Many Requests error and you have to wait until the window resets.
How do I avoid the token limit during bulk imports?
Use exponential backoff: start by waiting 1 second after a 429 error, then double the wait on every following error. Group requests through batch endpoints where Moneybird supports that, and put API calls in a queue with a maximum rate of 120 requests per 30 seconds as a buffer.
Can I use several API tokens to get around the limit?
That is technically possible with several Moneybird developer accounts, but it goes against the Moneybird terms of use. The better approach is to optimise your request pattern or to cache responses that do not change often.
What is the difference between OAuth tokens and API tokens in Moneybird?
OAuth tokens are meant for applications that operate on behalf of a user (third-party integrations). Personal API tokens are for direct access from your own scripts and tools. Both types of token fall under the same rate limit per administration.
How do I build a robust Moneybird integration that can handle rate limits?
Implement a request queue with rate limiting, cache responses for 5-15 minutes on endpoints that rarely change (such as contacts and products), use webhooks for real-time updates so you have to poll less, and monitor your API usage through the response headers X-RateLimit-Remaining and X-RateLimit-Reset.
