API integrations
API integration development
Do you type data in twice because your systems don't talk to each other? I build integrations that pass orders, customers and invoices along automatically, and that notice when something goes wrong.
Price indication Price on request
- Reply within 1 working day
- Fixed price up front
- One dedicated developer
// how an integration works
From payment to accounting, without retyping
Example: a customer pays in a webshop through Mollie. The integration creates the invoice in the accounting software and updates the CRM. If a system is briefly unreachable, the integration retries automatically.
Sync log Example data
- 09:14:02 Order #1042 paid Invoice created in accounting Done
- 09:14:03 Customer details #1042 CRM updated Done
- 09:21:47 Order #1043 paid Accounting briefly unreachable, retried after 30 sec. Retried
- 09:22:17 Order #1043 Invoice created (2nd attempt) Done
- 09:30:05 Refund #1038 Credit note created Done
- 09:41:19 New enquiry via website Contact created in CRM Done
Now Entering data twice, hunting for errors and checking afterwards.
With an integration Enter it once. The rest happens automatically, and you hear about it when something goes wrong.
What you get
Integrations that keep working
An integration is only good when you no longer have to think about it. You can see part of it in the example above.
-
No more double work
Orders, customers and invoices move from one system to the next automatically.
In the example The dot travelling from the webshop through the integration to accounting and CRM.
-
Automatic retries
If a system is briefly unreachable, the integration tries again later instead of losing data.
In the example The "Retried" row in the sync log.
-
Log and alerts
Every sync is recorded. If something really fails, you or your team get an alert.
In the example The sync log with a time and status per row.
-
Instant on every event
Where possible, the integration reacts right away through webhooks, for example to a payment or a new enquiry.
In the example The payment that flows straight into the integration.
-
Secure and documented
API keys stored safely, only the permissions that are needed, and documentation so you don't depend on me.
-
Maintenance when APIs change
When a vendor changes its API, I update the integration in time.
Who it is for
Is this a fit?
A good choice if
- You or your team retype data from one system into another.
- Your webshop, till, CRM or accounting get out of step and you hunt for errors afterwards.
- No standard integration exists, or it doesn't quite do what you need.
Not the right choice if
- A ready-made integration already does exactly what you want: that is often faster and cheaper.
- It is about a handful of actions a month: then custom work doesn't outweigh the cost.
Process
From separate systems to one flow
First work out exactly what should happen, including when things go wrong. Only then build.
-
Intro
Which systems, which data, and what should happen when something goes wrong?
-
Integration mapped
I check the APIs of your systems and map out the data flow, edge cases included.
-
Build and test
I build and test with test data, including errors, duplicate messages and unreachable systems.
-
Launch and monitor
The integration goes live with a log and alerts. Maintenance for API changes can be part of a support package.
Pricing
What does an API integration cost?
The price depends on the systems and how much logic sits in between. After a free intro call you get a fixed price.
Price indication
Price on request
Fixed price up front, after a free intro call.
What drives the price
- The number of systems and kinds of data
- One direction, or two-way sync
- The quality and documentation of the APIs
- How fast data needs to arrive: instantly, hourly or nightly
- Moving over existing data
FAQ
Good to know
What does an API integration cost?
It depends on the number of systems, the direction of the data and the quality of the APIs. After a free intro call you receive a fixed price.
Which systems can you connect?
Almost any system with an API or webhooks: webshops, payment providers such as Mollie and Stripe, CRM packages, accounting software, till systems and planning tools.
What if a system has no API?
Then we look at alternatives, such as an automated export and import. Sometimes a package with an API is the better choice; we discuss that honestly.
What happens when the integration fails?
Temporary errors are retried automatically. If it still fails after that, you get an alert and the message is kept, so nothing gets lost.
What if a vendor changes its API?
Vendors usually announce changes in advance. With a support package I update the integration in time.
Isn't Zapier or Make enough?
For simple steps it often is, and then I will recommend it. Custom work pays off with larger volumes, complex rules, sensitive data, or if you don't want monthly per-task costs.
Who owns the integration?
You do. You receive the source code and documentation, so you are not locked into one vendor.
Don't see your question? Ask me directly
Related
Often combined with
Contact
Book a free call about your integration
Briefly describe which systems you use and what you retype now. I reply within 1 working day.
Prefer direct contact?
- Email: contact@devaimlabs.com
- Phone: +31 6 38 52 30 99
- Reply within 1 working day