API and Integration

Marketplace API Integration

A marketplace never works on its own. Stock sits in the ERP, the accounting record in an e-invoicing service, the shipment movement with the carrier. The API layer's job is to turn those systems into one working whole; otherwise you need a team moving data by hand every day.

Start Free TrialGet a Quote
Product, order, stock, seller and content endpoints
REST APIProduct, order, stock, seller and content endpoints
Event-based notification; no constant polling needed
WebhooksEvent-based notification; no constant polling needed
Rule-based automation without writing code
WorkflowsRule-based automation without writing code
Scheduled import via XML, CSV and Excel
Bulk transferScheduled import via XML, CSV and Excel

When Does an API Solve the Integration, and When a Webhook?

A marketplace never works on its own. The seller's stock sits in their own ERP, the accounting record in an e-invoicing service, the shipment movement in the carrier's system, and the marketing data on an ad platform. The job of marketplace API integration is to turn those separate systems into one working whole; otherwise you have to hire a team that moves data by hand every day.

Integration runs in two directions and each needs a different tool. Pulling data in from outside (a seller's product and stock details, a supplier price list) is usually done with a scheduled bulk import or API calls. Pushing information out (a new order has been created, a shipment is on its way, a return has been opened) should be done with webhooks. Integrations that work by constant polling are both slow and wasteful.

The third matter is resilience. In real integrations the other system fails to respond, the same event is delivered twice, or a request times out. That is why idempotency keys, automatic retries, rate limits and an error queue are not optional extras but basic requirements. In PazaryeriSoft they come as part of the API layer.

Modules

Modules That Come Ready in the API Layer

REST API and Documentation

Resource-based endpoints, a consistent error format and pagination. The integration team works from example requests and responses.

Webhook Management

Which event goes to which address is defined from the panel; delivery history and failed attempts can be inspected.

API Key and Scope Management

A separate key for every integration; read-write scope and IP restrictions are defined per key.

Idempotency and Retries

The same request arriving twice does not create a duplicate record; failed calls are retried at increasing intervals.

Rate Limits and Quotas

A request limit is defined per integration; as the limit is approached, a warning is returned in the response headers.

XML, CSV and Excel Import

Scheduled imports keep seller and supplier catalogues synchronised; field mapping is done once.

Workflow Automation

Defining rules without writing code: on a given condition, send a notification, add a tag, restrict a seller or call an external service.

Bulk Export

Exporting order, product and earnings data for reporting and data warehousing.

Request Logs and Error Queue

Incoming and outgoing calls are logged; failed operations gather in a queue and can be replayed by hand.

Signed Request Verification

Webhook bodies are signed; the receiving side can verify that the request really came from you.

Provider-Agnostic Interfaces

Payment, shipping and invoicing providers connect through a shared interface; changing provider does not affect application code.

App Ecosystem

Additional modules and third-party apps connect to the platform through the same API layer.

Scope

API Surface and Event Notifications

On the left the endpoints you can call, on the right the events the system sends you. Most integrations use both together.

API surface

  • Product, variant, category and attribute endpoints
  • Stock and price updates, with bulk update support
  • Order listing, status updates and return operations
  • Seller, store and organisation management
  • Customer, address and favourite records
  • Content, campaign and coupon management
  • Token-based authentication and scope-based authorisation

Event notifications (webhooks)

  • Order created, paid, cancelled, return opened
  • Shipping label generated, shipment dispatched, delivered
  • Product published, rejected, out of stock
  • Seller application approved or suspended
  • Earnings accrued, withdrawal request approved
  • Source verification with a signed request body
  • Automatic retries at increasing intervals on failed delivery
Scenarios

The Six Most Commonly Built Integrations

All of them run through the same API layer; only the data direction and the trigger differ.

ERP and Stock Synchronisation

Stock and price changes in the seller's own system reach the platform through a scheduled import or API call; when an order is created it lands in the ERP via webhook.

e-Invoicing and Accounting

Commission invoices and earnings records are transferred to services such as Paraşüt and BirFatura. Reconciliation records are created automatically on the accounting side.

Shipping and Logistics Systems

Label generation and status updates run through carrier integrations; shipment movements are written onto the order automatically.

Marketing and Analytics

Order and product data is transferred to ad platforms and analytics tools; product feeds are refreshed regularly.

Listing on External Marketplaces

Your catalogue can be pushed to external channels; order and stock synchronisation is set up to run in both directions.

Custom Front Ends and Headless Use

You can write your own interface and use the platform purely as a data layer; the mobile app consumes the same API.

FAQ

Frequently Asked Questions

The questions integration teams ask most often.

They serve different directions. To pull data in from outside (a seller's product and stock details, a supplier price list) you use API calls or a scheduled bulk import. To push information out (a new order has been created, a shipment is on its way, a return has been opened) webhooks are the right tool. Solving that with constant polling creates both latency and unnecessary load; event-based notification removes both problems.
No. Write operations use an idempotency key; a second request with the same key does not create a new record but returns the result of the first. On the webhook side the same event can also be re-delivered, so the receiving system is advised to check the event id. This makes the repeat deliveries that are inevitable in real integrations harmless.
Failed webhook deliveries are retried automatically at increasing intervals. When the attempts are exhausted the record gathers in the error queue and can be replayed by hand from the panel. Because incoming and outgoing calls are logged, you can look back at which request ran when and with what response; most integration problems are resolved in minutes from these logs.
A separate key is generated for every integration. Read-write scope is defined per key; a reporting integration, for example, is given read access only. An IP restriction can optionally be added and a key can be revoked at any moment. That way an integration being compromised affects only that scope rather than the whole system.
Yes, a request limit is defined per integration. As the limit is approached, the remaining quota is returned in the response headers so the client can slow itself down. For bulk work we recommend using the bulk update endpoints or a scheduled import rather than making calls one by one; it is faster and it does not eat the quota.
Yes, that is what the workflow editor is for. You define rules made of conditions and actions: on a given state, send a notification, tag an order, restrict a seller or call an external service. A significant share of simple integrations is solved this way without a developer; the API is needed only for more complex scenarios.
Yes. Sellers can connect their own ERP or stock systems over the API, or set up a scheduled import in XML, CSV or Excel format. Field mapping is done once at initial setup and subsequent imports use the same template. AI-assisted field matching shortens how long it takes to connect catalogues in unfamiliar formats.

Related Pages

Marketplace Mobile App

The iOS and Android app that consumes the same API layer.

Headless E-Commerce

The model where you use the platform purely as a data layer and write your own front end.

Marketplace Payment System

Payment institution integrations that connect through a provider-agnostic interface.

All Marketplace Features

The full account of the API, workflow and data transfer modules.

Let's Plan Your Integrations Together

Let's work out which systems will connect, the data directions and the triggers.

Start Free TrialGet a Quote

REST API + Webhooks · Workflow automation · 24/7 support