Start a project

Floor 01 · Build

API integration services. Systems that talk.

API integration services connect your website, your apps and the online services they depend on, such as payment providers, booking tools, maps, email and AI models, so data moves between them on its own. yop builds and maintains API integrations from Tallinn, with monitoring and logs, and the code, keys and accounts stay in your name.

Integrations

What do API integration services include?

An API integration lets two systems exchange data without a person in between: a paid checkout confirms the booking, a sign-up on the site lands in the email tool, a parcel status appears in the customer’s account. The work is less about the code than the details around it: which system is the source of truth, how the fields map, what happens when one side is down.

We build integrations on REST and GraphQL APIs, webhooks and, where needed, older SOAP or file-based interfaces. Each one gets logging, retries and alerts, so a failed sync is noticed within minutes, not at the end of the month.

Integrations inside business systems, such as accounting, e-invoicing and marketplace connections, are built by our sister company pirdir.

  • Payments. Stripe, PayPal, Klarna and local providers linked to checkouts, subscriptions and refunds.
  • Website and app data. Accounts, forms and content shared between your site, your app and your own API.
  • Third-party services. Maps, booking, messaging, email and AI APIs wired into your product.
  • Online shops. Products, stock and orders kept in step between your store and the services around it.

Failure drill

If something breaks, nothing gets lost.

A paid order travels from the payment provider to your shop. Pick what goes wrong and read how the integration answers.

Illustration. Real retry times and limits follow each provider’s own rules.

Payment webhook · failure drill

Checkout · order #1042

2 × house blend, 250 g

€38.00 · paid by card

Payment providersent
Your APIall good
  • verify signature
  • retry
  • dedupe
  • queue
  • adapter
Shop200 OK
Email202 sent

integration.logtail -f

  1. 09:58:00INFOworker up · listening on /webhooks/payment
  2. 09:58:00INFOroutes: /orders to the shop · /receipts to mail
  3. 09:58:00INFOretries: 5 attempts, from 30 s up to 30 min apart
  4. 09:58:01OKhealth check · shop 200 · mail 200
  5. 09:58:01INFOqueue empty · alerts go to the on-call owner
  6. 10:42:07INpayment.paid #1042 · key pay_1042
  7. 10:42:07OKsignature checked · key is new
  8. 10:42:07200POST /orders/1042/paid · 86 ms
  9. 10:42:07202POST /receipts #1042 · 47 ms
  10. 10:42:07200provider answered · 140 ms in all
  11. 10:44:12INpayment.paid #1043 · key pay_1043
  12. 10:44:22504POST /orders/1043/paid · no answer in 10 s
  13. 10:44:52RETRYattempt 2 of 5 after 30 s · 504
  14. 10:46:52RETRYattempt 3 of 5 after 2 min
  15. 10:46:52200POST /orders/1043/paid · 310 ms · paid
  16. 10:51:30INpayment.paid #1044 · key pay_1044
  17. 10:51:30200POST /orders/1044/paid · 92 ms
  18. 10:51:33INpayment.paid #1044 · key pay_1044 again
  19. 10:51:33SKIPkey pay_1044 already handled · no second order
  20. 10:51:33200provider answered · one order, one email
  21. 11:03:15INpayment.paid #1045 · key pay_1045
  22. 11:03:15200POST /orders/1045/paid · 88 ms
  23. 11:03:15503POST /receipts #1045 · mail service down
  24. 11:03:15QUEUEreceipt #1045 held · 3 waiting · retry every 60 s
  25. 11:03:16ALERTon-call owner told: mail down since 11:01
  26. 11:20:02WARNshop sent Sunset: 31 Mar 2027 for API v1
  27. 11:20:02INFOv2 renames “amount” to “total”
  28. 11:21:40TESTadapter v2 on staging · 48 of 48 passed
  29. 11:22:05200POST /v2/orders/1046/paid · 95 ms
  30. 11:22:05OKswitched to v2 before v1 is retired

Normal: paid, recorded, emailed in under a second

Integration words

Six terms worth knowing.

Idempotency
Making sure the same request, sent twice, has the effect of one. It stops double orders and double charges.
OAuth
A standard way for one app to get limited access to another account without ever seeing its password.
Rate limit
The number of calls an API accepts in a period. Integrations queue and pace their calls to stay under it.
Sandbox
A test copy of a service where payments and messages are fake, so everything can be tried safely.
Source of truth
The one system whose value wins when two systems disagree about the same field.
Webhook
A message one service pushes to another as soon as an event happens, like a payment clearing.

Compare

A custom integration or a connector app?

A custom API integration compared with a ready-made connector app
A custom API integration compared with a ready-made connector appCustom integrationOur pickReady-made connector
Fits your data and rulesYesWithin its settings
Monitoring and alertsBuilt inVaries
Monthly feeHosting onlyPer connector or per task
Exceptions handledThe way you decideThe way the vendor decides
Best forCore flows, high volume, special rulesSimple, standard links

How it runs

Four steps to data that flows.

v0.1
01

Map

A written map of each system, field and rule, naming which system holds the master copy.

v0.2
02

Build

Connectors built against test accounts, with logging, retries and alerts.

v0.3
03

Test

Real cases run end to end, including the awkward ones: duplicates, refunds, timeouts.

v1.0
04

Run

Go-live, monitoring, and a fix when a vendor changes its API.

Cost

What sets the price of an integration.

Two systems with good APIs are the simple case. These are the things that add work.

Large

Number of systems

Each extra system brings its own fields, limits, test accounts and failure modes.

Large

Old interfaces

SOAP services, file drops and database access need more care than a modern REST API.

Medium

Real time or scheduled

Instant webhooks need queues and retries; a nightly sync is simpler to build and watch.

Medium

Unusual rules

Partial refunds, split shipments and currency rounding are where most of the testing time goes.

Small

Data volume

High volume needs paging and pacing, but rarely changes the design itself.

Small

Monitoring needs

Logs, alerts and a named owner are always included; dashboards for them are optional.

After launch

What happens when an API changes?

APIs change: vendors release new versions, retire old fields and change their limits. Each integration yop builds has logs and alerts, and we follow the change notices of the APIs we maintain, so updates are planned before the old version stops working.

Maintenance can run at a fixed monthly price, or your own team can take it over with the documentation we hand over.

Your systems

List your tools, we draw the links.

Tell us which systems you use and where people retype data between them. Our reply comes within two working days and covers an integration map.

Questions

Asked about integrations.

What do API integration services do?

API integration services wire a company’s separate software together through its APIs, so records travel between systems without manual copying. yop maps the data, builds the connections, monitors them and maintains them when the APIs change.

yop prices integrations as a fixed price per phase after mapping the systems and data. The number of systems, the data volume and how unusual the rules are decide the scope.

A link between two systems with good APIs is often live within weeks. Integrations with old systems, many rules or several countries take longer.

Often, yes. We use database access, file exchange or a small API layer in front of the old system, chosen by what is stable and allowed.

Websites, mobile apps, payment providers, online shops, booking and messaging tools, email platforms, AI models and most SaaS tools with a documented API.

Every integration has logs, retries, alerts and a clear owner for each data field. Failed syncs are flagged within minutes so they can be fixed before anyone notices.

Yours. Code, credentials and vendor accounts are opened in your name and written up, so a different team could step in.