# API Integration Explained: How to Connect Your ERP, E-commerce, e-Invoicing and Banking Systems

> API integration explained: how REST APIs, webhooks and EDI differ, how to link ERP, e-commerce, e-invoicing and banks, and an 8-step plan to end double entry.

Source: https://digitalbridge.com.tr/en/blog/api-integration-explained.html
Publisher: Digital Bridge Teknoloji (https://digitalbridge.com.tr)
Topic: Software Development
Published: 2026-10-21 · Updated: 2026-10-22

API integration is the automatic exchange of data between two or more software systems through defined gateways called [APIs (application programming interfaces)](https://digitalbridge.com.tr/en/glossary.html#api). A web-shop order goes straight to the ERP, stock updates on both sides, the invoice reaches the e-invoicing provider and a courier is booked, with no one retyping data. Done well, it removes double entry and delays.

## Key takeaways

- API integration lets software exchange data through defined interfaces without anyone retyping it, removing double entry and delays.
- The main methods are REST APIs, webhooks, scheduled file transfer, EDI and RPA; for permanent flows, APIs combined with webhooks are the most robust.
- According to TurkStat, only 28.3% of Turkish enterprises with 10+ employees used ERP in 2025; many companies still move data by hand.
- The most common links in Türkiye connect the ERP with web shops, marketplaces, e-invoicing providers, banks and couriers.
- A robust project defines data ownership, field mapping, error and retry rules, duplicate prevention and maintenance responsibility from the outset.

## Why API integration matters: disconnected systems in most companies

As of 2026, a typical mid-sized company runs several separate pieces of software side by side: an [ERP (enterprise resource planning)](https://digitalbridge.com.tr/en/glossary.html#erp) system or accounting package, a web shop or [B2B dealer portal](https://digitalbridge.com.tr/en/blog/b2b-dealer-portal-guide.html), one or more marketplace dashboards, an e-invoicing provider, the courier's booking screen and the bank's online portal. Each does its own job well. The problem is the gap between them. On the HR side, one of the most common links is [time and attendance payroll integration](https://digitalbridge.com.tr/en/blog/time-attendance-payroll-integration.html), which moves timesheets into payroll.

People usually fill the gap between systems. Someone in sales operations downloads marketplace orders into a spreadsheet and keys them into the ERP one by one; the warehouse updates stock on the web shop by hand at the end of the day; finance downloads the bank statement and matches receipts to customer accounts. During the day a product shown as in stock may already be sold, and an order marked "shipped" may still be sitting in the warehouse. The report a manager sees depends on which system it was pulled from.

## What does the lack of integration cost?

A large share of Turkish businesses still lacks an integrated core system. According to the [TurkStat ICT Usage in Enterprises Survey 2025](https://veriportali.tuik.gov.tr/tr/press/54012), 28.3% of Turkish enterprises with 10+ employees used ERP software, 12.0% used CRM and only 6.5% used business intelligence (BI) software. The TurkStat figures point to a lot of data still being moved by hand between spreadsheets, emails and standalone programs.

At the same time, the number of digital channels that need connecting keeps rising:

> According to the [TurkStat ICT Usage in Enterprises Survey 2026](https://veriportali.tuik.gov.tr/tr/press/58021), the share of Turkish enterprises selling via the internet or EDI (electronic data interchange) rose from 13.6% in 2024 to 17.1% in 2025, reaching 29.7% among firms with 250+ employees.

The same is true of statutory documents. Türkiye requires many businesses to issue invoices and dispatch notes electronically through the Revenue Administration's systems (e-Fatura and e-İrsaliye). The [Turkish Revenue Administration (GİB) 2025 Annual Activity Report](https://cdn.gib.gov.tr/api/gibportal-file/file/getFileResources?objectKey=arsiv/fileadmin/faaliyetraporlari/2025/2025_faaliyet_raporu.pdf) shows the number of taxpayers using e-İrsaliye rising from 402,985 in 2024 to 632,288 at the end of 2025. Every new e-document obligation adds another data flow between the ERP and the provider.

When data flows between systems run by hand, the cost shows up in three places: staff time (the same data entered several times), errors (wrong stock, wrong prices, missing invoices) and decision speed (managers acting on out-of-date figures). Bringing data from several systems together for reporting is the job of a [data warehouse and ETL](https://digitalbridge.com.tr/en/blog/data-warehouse-etl-guide.html).

## How does API integration work, and which method should you use?

Think of an API as a waiter in a restaurant. You do not walk into the kitchen (the system); you give the waiter (the API) a defined order and receive a defined response. The system owner decides through the API which data is exposed, to whom and with what permissions.

The key difference between a REST API and a webhook is direction: with a REST API the system that needs data asks and waits for a response, while with a webhook the system that holds the data notifies the other side the moment an event occurs. Not every integration is built the same way. The most common options:

| Method | How it works | Best suited to | Watch out for |
|---|---|---|---|
| **REST API (request-response)** | One system asks another to "return this order" or "save this record" | Record-based work: orders, accounts, stock | Rate limits and error handling |
| **Webhook (event notification)** | A system notifies another the moment something happens | New orders, payment confirmations, delivery status | Retrying missed notifications |
| **Scheduled file transfer** | CSV/XML files are moved at set times | Legacy systems without an API (for a lasting fix, see [legacy software modernisation](https://digitalbridge.com.tr/en/blog/legacy-software-modernization.html)), bulk price lists | Latency — no intraday accuracy |
| **EDI / standard documents** | Parties exchange documents in an agreed standard format | Trading with large suppliers and retail chains ([what EDI is](https://digitalbridge.com.tr/en/blog/what-is-edi.html)) | Format compliance and testing |
| **Screen automation (RPA)** | A bot uses the screens a person uses | Systems with no API that cannot be changed | Maintenance when screens change |

For permanent, high-volume flows, APIs combined with webhooks give the most robust result. We explain when screen automation makes sense for systems without an API in [what is RPA](https://digitalbridge.com.tr/en/blog/rpa-explained.html). When choosing new packaged software, always ask whether it offers a documented, versioned API; integration capability is one of the deciding criteria in the [custom vs off-the-shelf software](https://digitalbridge.com.tr/en/blog/custom-vs-off-the-shelf-software.html) decision.

## Which API integrations do businesses in Türkiye most often need?

- **ERP ↔ web shop and marketplaces:** orders flow into the ERP, and stock and prices are updated on every channel from a single source. See our [marketplace integration](https://digitalbridge.com.tr/en/blog/marketplace-integration.html) and [B2B ecommerce ERP integration](https://digitalbridge.com.tr/en/blog/b2b-ecommerce-erp-integration.html) guides for the detail.
- **ERP ↔ e-Invoice / e-Archive / e-Dispatch provider:** the document is created in the ERP, sent to the accredited provider and its status is returned. We cover this in detail in our [e-invoice integration guide](https://digitalbridge.com.tr/en/blog/e-invoice-integration-turkey.html).
- **ERP ↔ bank:** account movements are fetched automatically and receipts matched to customer accounts. We cover the matching rules in [bank reconciliation automation](https://digitalbridge.com.tr/en/blog/bank-reconciliation-automation.html).
- **Orders ↔ courier:** shipments are booked automatically and the tracking number returns to the customer and the system. The same data can answer "where is my order?" through a [WhatsApp business chatbot](https://digitalbridge.com.tr/en/blog/whatsapp-business-chatbot.html).
- **CRM ↔ ERP:** sales and finance see the same customer balance and order status. We cover the sales side in our [CRM sales pipeline guide](https://digitalbridge.com.tr/en/blog/crm-sales-pipeline-guide.html).
- **Production and field systems ↔ ERP:** shop-floor, warehouse and field data reach the ERP in real time, and vehicle location, mileage and fuel data can join the same flow through a [fleet management system](https://digitalbridge.com.tr/en/blog/fleet-management-system.html). The ISA-95 model that defines the layers between the shop floor and ERP, and where MES sits in that flow, is explained in [MES vs ERP](https://digitalbridge.com.tr/en/blog/mes-vs-erp.html).

Why the ERP sits at the centre of all this is covered in our guide to [ERP for SMEs](https://digitalbridge.com.tr/en/blog/erp-for-smes.html). Sector-specific flows follow the same logic: [hospital queue and appointment management](https://digitalbridge.com.tr/en/blog/hospital-queue-appointment-management.html), for example, links appointment data in the hospital information system to calling screens.

## How do you run an API integration project? Eight steps

1. **Decide who owns each piece of data.** Choose one source of truth per data type: does the ERP own prices, or the web shop? Skip this decision and two systems will end up overwriting each other.
2. **Map the flows.** Which event (new order, return, stock change) goes from which system to which, and how often? A one-page flow diagram is enough.
3. **Write down the field mapping.** Product codes, units, VAT rates and account codes need to be matched on both sides in a table.
4. **Define errors and retries.** What happens when the other system does not respond? Records should wait in a queue, be retried and, after a set number of attempts, be flagged to someone responsible.
5. **Prevent duplicates.** Give every record a unique reference so the same order is never transferred twice. Cleaning up duplicates that already exist in source systems is a separate job, covered in [data quality and duplicate records](https://digitalbridge.com.tr/en/blog/data-quality-duplicates.html).
6. **Log and monitor.** Every transfer — when it ran and with what result — should be visible, so "why didn't this order reach the ERP?" can be answered in minutes.
7. **Test real scenarios in a test environment.** Returns, partial shipments, cancellations and price changes must be tested before go-live.
8. **Plan ownership and maintenance.** Who updates the integration when the other side releases a new API version? The contract should answer that.

Guides to the systems integration connects, such as ERP, CRM, WMS and dealer portals, are collected in [our Software Development articles](https://digitalbridge.com.tr/en/blog/topic/yazilim.html).

## API integration security: every connection is a new door

An API integration opens a new route for data to leave and enter the organisation. If it is unclear who uses the integration route and with what rights, the risk grows. According to the [Verizon 2026 Data Breach Investigations Report](https://www.verizon.com/business/resources/T1ae/reports/2026-dbir-data-breach-investigations-report.pdf), breaches involving a third party rose 60% in a year to 48% of all breaches.

The basic rules are simple: API keys never go into source code or emails but live in a secure vault, and each integration accesses only the data it needs. Keys are rotated regularly, and access is revoked as soon as a partnership ends. Integrations that move personal data must also appear in your data inventory under KVKK, Türkiye's Personal Data Protection Law No. 6698.

In automotive supply chains the most demanding integration is message exchange with the vehicle maker; we cover DELFOR and DESADV flows separately in our [automotive EDI integration](https://digitalbridge.com.tr/en/blog/automotive-edi-integration.html) guide.

## How does Digital Bridge deliver API integration?

- **We map your current systems.** Through our [API integration service](https://digitalbridge.com.tr/en/software-solutions/api-integration.html) we list the software you use, which systems expose APIs and where data is still moved by hand today.
- **We choose the right method.** A direct connection where an API exists; a scheduled transfer or screen automation where it does not. Hardware links — machines, terminals, sensors — are handled by the same team through our [system integrations](https://digitalbridge.com.tr/en/technology-hardware/system-integrations.html) work, so there is no gap in responsibility between software and hardware.
- **We design a single data flow.** Where several systems must work together in one business process, we design the order, stock and invoice flow end to end with our [integrated systems](https://digitalbridge.com.tr/en/software-solutions/integrated-systems.html) approach, and connect sales channels through [e-commerce and B2B](https://digitalbridge.com.tr/en/software-solutions/e-commerce-b2b.html) platforms. [SmartSales](https://digitalbridge.com.tr/en/smart360/smartsales.html), the e-commerce product in our Smart family, feeds the storefront, marketplaces and product feeds from a single catalogue; its headless API uses separate read and management tokens, and the management token writes only catalogue and stock data.
- **We build security in from the start.** Key management, permission boundaries and logging follow the principles of our [cyber security consultancy](https://digitalbridge.com.tr/en/consultancy/cyber-security.html).
- **We bring emailed documents into the flow.** Where supplier invoices arrive by email, [SmartMail](https://digitalbridge.com.tr/en/smart360/smartmail.html), part of the [Smart360](https://digitalbridge.com.tr/en/smart360.html) suite, extracts fields such as totals, VAT, dates, document number and tax number from the attached invoice PDF without the file being downloaded, and the attachment can be saved to SmartFiles in one click.
- **We make the result visible.** Integrated data can feed a [BI dashboard](https://digitalbridge.com.tr/en/data-analytics/bi-dashboard.html) so management sees one version of the numbers.

Scope, phases and cost are set out in a written proposal; we do not push a packaged product.

To decide which process to integrate first, use the prioritisation matrix in our article on [which business processes to automate first](https://digitalbridge.com.tr/en/blog/which-processes-to-automate-first.html).

## Next step

Start with a sheet of paper: list every piece of software your company uses and draw an arrow wherever data is moved between them by hand. The system with the most arrows shows where integration should begin. Bring that diagram and [contact us](https://digitalbridge.com.tr/en/contact.html) — we will work out together which connection will pay back first.

## Frequently Asked Questions

### Is API integration the same as system integration?

API integration is the most common form of system integration. System integration is the broader term: it also covers file transfers, EDI, direct database connections, screen automation and hardware links such as machines and terminals. Most projects combine several methods: systems with an API connect directly, while those without one join the flow through file transfer or RPA.

### Can we integrate a program that has no API?

In most cases, yes. If the program can export data, a scheduled file transfer can be set up; if it cannot, an RPA bot can enter data through its screens. In the longer term, moving to a system with an API or adding a middleware layer can also be considered. The right option depends on data volume and how critical up-to-date data is.

### How long does API integration take, and what drives the cost?

Both depend on the number of systems, how mature and well documented their APIs are, how complex the field mapping is, and how many exception scenarios, such as returns, cancellations and partial shipments, need handling. There is no single list price, which is why we give timelines and costs after a requirements analysis, phase by phase, in a written proposal.

### What happens if the other party changes its API?

Providers usually change APIs through new versions and keep the old version available for a period. If maintenance responsibility and monitoring are defined from the outset, the change is spotted in time and the integration is updated. The contract should therefore state who carries out compatibility work when a new version ships and who receives error alerts.

### Does API integration create data protection risks?

Every integration that moves personal data is a data transfer activity. Only the necessary data should be transferred, API keys must be stored securely, access should be logged and the transfer recorded in your data inventory. Where data goes to a system hosted outside Türkiye, the transfer needs separate assessment under the cross-border transfer rules of KVKK.

### What is the difference between a REST API and a webhook?

With a REST API, one system sends a request to another and waits for the response; it is used to read or write order, account or stock records. With a webhook, the source system notifies the other side automatically the moment an event, such as a new order or payment confirmation, occurs. Permanent, high-volume flows use both together, with a retry rule for missed notifications.

### Which system should API integration start with?

Start with the systems between which the most data is moved by hand. A simple diagram listing every piece of software in the company, with arrows wherever data is transferred manually, reveals this quickly. The system with the most arrows is usually the ERP, and the web shop, marketplaces, e-invoicing provider, bank and courier connect to that hub.
