ERP and accounting
Two-way sync of products, stock, customer accounts, orders and invoices with your ERP or accounting package.
API integration services
Enter the data once. Let every system receive it.
Our API integration services connect the software you already use, such as ERP, accounting, your online store, shipping and messaging, so an order, payment or stock change recorded in one place reaches the others automatically. Kodem designs, builds, documents and monitors these connections, usually without replacing the systems themselves.
- Two-way data flow
- Tested before it touches live data
- Errors logged and alerted
The problem
Copying figures between screens is a hidden cost.
In many companies an order arrives on the website, is typed into the ERP, copied to the accounting package, entered again on the carrier's site and finally confirmed to the customer by message. Each step takes time and each copy is a chance for a mistake.
An integration replaces those copies with a defined data flow. We map which system is the source of truth for each record, what triggers a transfer and what should happen when one side is unavailable, then build and test the connection before it goes live.
In shortWe connect existing systems through their APIs, or build an API where none exists, so records move between them without manual re-entry.
- Orders typed into more than one system
- Stock figures that differ between store and warehouse
- Invoices or delivery notes produced by hand
- Customer updates sent manually after every status change
What we connect
If it has an API, it can usually be connected.
The exact list for your project is confirmed in the analysis stage, after we have read each system's documentation.
Online stores and marketplaces
Products, prices, stock and orders kept in step between your own store and the marketplaces you sell on.
E-invoicing and government services
Invoices and documents sent to e-invoicing systems and, where required, to official online services.
Shipping carriers
Labels, tracking numbers and delivery status pulled from carriers into your order screens.
SMS, email and WhatsApp
Order, booking and status messages sent automatically when a record changes.
Your own API
A documented REST or GraphQL API so partners, dealers or a mobile app can read and write your data.
How we work
Analysed, documented and tested before go-live.
Each stage is agreed in writing, and tests run against sandbox or copy data, not your live records.
- System analysisWe study your systems, their data structures and documentation, and agree what each integration must achieve.
- DesignWe choose the protocol (REST, GraphQL or SOAP), define the data mapping and the security layer, and price the work line by line.
- Build and documentationConnections and any middleware are written and documented, so every field and rule is traceable.
- Testing, launch and monitoringEnd-to-end and load tests and a security review, then go-live with error logging and alerts.
Security and reliability
A connection is only useful if you can rely on it.
Authorised access
OAuth 2.0 or signed tokens, HTTPS only, IP allow lists where the other side supports them.
Rate limits
Requests are throttled so neither system is overloaded, and limits set by third parties are respected.
Logs and alerts
Every transfer is logged; failures raise an alert to our team rather than disappearing silently.
No downtime to connect
An adapter layer sits beside your current system, so daily work continues while the integration is built.
Selected work
Integrations running inside real projects.
Anonymised. One connects to government services for authorisation; the other sends each order to three channels at once.
Classified ads platformMarketplace · Web application1,034 automated checks, 0 errors
A classifieds platform integrated with Türkiye's government services and ready for regulation
An end-to-end platform for property, vehicle and product listings: listing fields that change by category, search, messaging, price assessment and moderation.
- Integration with the Ministry of Trade's EİDS system (authorisation via Türkiye's e-Government gateway)
- SMS and email notifications, 13 email templates
- Personal data export and anonymisation under Turkish data protection law (KVKK), with legally required logging
- Around 67 database tables, 15 test suites
Wholesale accessories manufacturerB2B catalogue · Quotes and orders3 channels per order, at once
Each order lands in the dashboard, on WhatsApp and in email at once
An ordering system for dealers, with a colour-variant product catalogue, a persistent quote basket and a seven-stage order flow.
- Orders delivered to three channels simultaneously
- Every uploaded image converted to WebP in three sizes
- Connected structured data for products, catalogue and FAQ
- Payment receipt uploads protected by authorised access
Projects are anonymised: we do not publish client names without written consent. Figures are from handover-day tests; live values may change over time.
Is this for you?
When integration is the right next step.
A good fit if
- Your systems work, but nobody wants to replace them, only to connect them
- The other systems offer an API, or allow file or database exchange
- You want one team responsible for the connection after launch
Not the right fit if
- A system offers no API and its supplier will not allow any form of access
- The underlying system is so outdated that connecting it would only delay its replacement
In the second case, modernising the old system is often the better investment.
Questions
Questions about API integration
What is the difference between REST and GraphQL?
REST uses fixed addresses for each type of resource and is the most widely supported standard. GraphQL uses a single address where the caller asks for exactly the fields it needs, which suits mobile apps and data with many relationships. We choose with you according to the systems involved.
Which systems can you integrate?
ERP and accounting packages, online stores and marketplaces, shipping carriers, e-invoicing services, SMS and email services, WhatsApp and more. Any system with a documented API can generally be connected. Integration with local payment providers is assessed during scoping.
Can you integrate while our current systems keep running?
Yes. We add an adapter or middleware layer beside the existing system, test everything in a separate environment, and switch on the live connection only after it has been verified.
How is the integration secured?
Access uses OAuth 2.0 or signed tokens over HTTPS, with rate limits, IP allow lists where supported, and encrypted transfer. Credentials are stored on the server, never in a browser or app.
Who maintains it when the other system changes its API?
We do. Connections are monitored, and when a third party changes or retires its API we update the integration. The scope of support and our response times are written into the contract.
Who owns the integration code and the data?
Kodem develops your software, hosts it on servers in Türkiye and keeps it up to date. The source code stays with Kodem. Your domain is registered in your name, and your content and data are always yours.
How is an integration priced?
After the analysis you receive an itemised quote in USD, listing each connection and its data flows. Once approved, the price is fixed; additional connections are quoted separately.
List the systems you use. We will draw the data flow.
A free video call about your software and where data is copied by hand, then a written integration map and an itemised quote in USD.