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.
What we connect
The links we build most.
Payments and subscriptions
Checkout, recurring billing, refunds and payment status kept in step with your site or app.
Online shops
Store orders, stock and prices synced with the services around the shop, on a schedule or in real time.
Website and app back ends
Your website and your mobile app reading and writing the same data through one API.
Third-party APIs
Maps, booking, messaging, email and AI services added to your product, with the keys stored safely.
Webhooks and events
Instant updates between services when something happens, with retries when a call fails.
Your own API
A clean, documented API for your own software, so partners and future tools can connect to 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.
Checkout · order #1042
2 × house blend, 250 g
€38.00 · paid by card
- ok
- waiting
- down
- changed
- verify signature
- retry
- dedupe
- queue
- adapter
integration.logtail -f
- 09:58:00INFOworker up · listening on /webhooks/payment
- 09:58:00INFOroutes: /orders to the shop · /receipts to mail
- 09:58:00INFOretries: 5 attempts, from 30 s up to 30 min apart
- 09:58:01OKhealth check · shop 200 · mail 200
- 09:58:01INFOqueue empty · alerts go to the on-call owner
- 10:42:07INpayment.paid #1042 · key pay_1042
- 10:42:07OKsignature checked · key is new
- 10:42:07200POST /orders/1042/paid · 86 ms
- 10:42:07202POST /receipts #1042 · 47 ms
- 10:42:07200provider answered · 140 ms in all
- 10:44:12INpayment.paid #1043 · key pay_1043
- 10:44:22504POST /orders/1043/paid · no answer in 10 s
- 10:44:52RETRYattempt 2 of 5 after 30 s · 504
- 10:46:52RETRYattempt 3 of 5 after 2 min
- 10:46:52200POST /orders/1043/paid · 310 ms · paid
- 10:51:30INpayment.paid #1044 · key pay_1044
- 10:51:30200POST /orders/1044/paid · 92 ms
- 10:51:33INpayment.paid #1044 · key pay_1044 again
- 10:51:33SKIPkey pay_1044 already handled · no second order
- 10:51:33200provider answered · one order, one email
- 11:03:15INpayment.paid #1045 · key pay_1045
- 11:03:15200POST /orders/1045/paid · 88 ms
- 11:03:15503POST /receipts #1045 · mail service down
- 11:03:15QUEUEreceipt #1045 held · 3 waiting · retry every 60 s
- 11:03:16ALERTon-call owner told: mail down since 11:01
- 11:20:02WARNshop sent Sunset: 31 Mar 2027 for API v1
- 11:20:02INFOv2 renames “amount” to “total”
- 11:21:40TESTadapter v2 on staging · 48 of 48 passed
- 11:22:05200POST /v2/orders/1046/paid · 95 ms
- 11:22:05OKswitched to v2 before v1 is retired
›
Normal: paid, recorded, emailed in under a second
Integration words
Six terms worth knowing.
- IIdempotency
- Making sure the same request, sent twice, has the effect of one. It stops double orders and double charges.
- OOAuth
- A standard way for one app to get limited access to another account without ever seeing its password.
- RRate limit
- The number of calls an API accepts in a period. Integrations queue and pace their calls to stay under it.
- SSandbox
- A test copy of a service where payments and messages are fake, so everything can be tried safely.
- SSource of truth
- The one system whose value wins when two systems disagree about the same field.
- WWebhook
- 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 | Custom integrationOur pick | Ready-made connector |
|---|---|---|
| Fits your data and rules | Yes | Within its settings |
| Monitoring and alerts | Built in | Varies |
| Monthly fee | Hosting only | Per connector or per task |
| Exceptions handled | The way you decide | The way the vendor decides |
| Best for | Core flows, high volume, special rules | Simple, standard links |
How it runs
Four steps to data that flows.
Map
A written map of each system, field and rule, naming which system holds the master copy.
Build
Connectors built against test accounts, with logging, retries and alerts.
Test
Real cases run end to end, including the awkward ones: duplicates, refunds, timeouts.
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.
Number of systems
Each extra system brings its own fields, limits, test accounts and failure modes.
Old interfaces
SOAP services, file drops and database access need more care than a modern REST API.
Real time or scheduled
Instant webhooks need queues and retries; a nightly sync is simpler to build and watch.
Unusual rules
Partial refunds, split shipments and currency rounding are where most of the testing time goes.
Data volume
High volume needs paging and pacing, but rarely changes the design itself.
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.
- first release on a test link
- write the process down
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.
- From
- you@your-company.com
- To

Anıl or Hatice- Send
- Tell us which systems you use and where people retype data between them.
- Reply
- Within two working days
Questions
Asked about integrations.
What do API integration services do?
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.
How much do API integration services cost?
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.
How long does an API integration take?
A link between two systems with good APIs is often live within weeks. Integrations with old systems, many rules or several countries take longer.
Can you integrate legacy systems without an API?
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.
Which systems can you integrate?
Websites, mobile apps, payment providers, online shops, booking and messaging tools, email platforms, AI models and most SaaS tools with a documented API.
How do you keep integrations reliable?
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.
Whose are the integration code and the API keys?
Yours. Code, credentials and vendor accounts are opened in your name and written up, so a different team could step in.
Floor 01 · Build
More on the Build floor
Custom software, SaaS, apps and AI, owned by your company.
Software built around how your company already works.
Subscription products with accounts, plans and billing.
The smallest real product that paying users can try.
iOS and Android apps people keep on their home screen.
The numbers and screens your team opens every morning.
Back office, genealogy and commissions, built for your plan.
AI and automation inside the tools you already use.







