Integrate ONIX Metadata with Your Existing Business Systems
Organizations working with book metadata often already have established systems for managing products, customers, inventory, commerce, or internal business processes.
That system might be a custom application, PIM, ERP, publishing platform, internal database, online store, or another management solution.
You don’t need to replace it to work with ONIX.
ONIXEDIT Server can act as the integration layer between ONIX metadata and your existing systems, whether you need to generate ONIX from your own data, ingest ONIX received from partners, or make ONIX data available to another application through an API.
Watch: Integrating ONIX with an in-house system
In this demonstration, we show how ONIXEDIT Server can automatically ingest ONIX and Excel files, process the resulting products, and make their metadata immediately available through its REST API.
One integration platform, many types of systems
ONIXEDIT Server isn’t limited to traditional publishing databases.
It can be integrated with systems such as:
-
ERP systems
-
PIM platforms
-
Proprietary or in-house applications
-
Publishing and title-management systems
-
SQL or other business databases
-
E-commerce and online bookstore platforms
-
Distributor and aggregator systems
-
Internal web applications
-
Other systems that need to produce or consume ONIX metadata
The objective is simple: let each system continue doing what it does best while ONIXEDIT Server handles the ONIX-specific complexity.
Metadata can flow in either direction
Integration isn’t limited to publishers sending ONIX to recipients.
From your system to ONIX
A publisher, distributor, or other metadata provider can maintain information in its existing application and use ONIXEDIT Server to transform, validate, manage, and distribute that information as ONIX.
This avoids rebuilding complete ONIX support inside the source application.
From ONIX to your system
The opposite workflow is equally important.
A distributor, aggregator, reseller, or retailer may receive ONIX files from hundreds or thousands of data providers and need that information inside its own PIM, ERP, commerce platform, or proprietary database.
ONIXEDIT Server can ingest those incoming files and expose the resulting metadata through its REST API in a structure the destination system can use.
This is one of the workflows demonstrated in the video.
Automate incoming ONIX and other metadata
ONIXEDIT Server’s Automated Ingestion Agent (AIA) can monitor configured entry points and automatically process incoming metadata and media files.
The source doesn’t necessarily have to be ONIX.
ONIXEDIT Server can work with ONIX 2.1, ONIX 3 and ONIX 3.1, as well as structured flat files such as Excel, CSV and tab-delimited files when the appropriate mappings are configured.
That makes it possible to normalize metadata from different sources before exposing it to your own applications.
Access ONIX metadata through the REST API
Once the metadata is available in ONIXEDIT Server, your applications can access it programmatically using the REST API.
Products can be retrieved as XML or JSON, and applications can perform searches using ONIX metadata fields.
More importantly, your integration does not necessarily have to consume the complete ONIX record.
You can request and structure the specific information your application needs.
For example, a reseller might retrieve only:
ISBN → Title → Contributors → Price → Availability → Cover image
while an internal metadata platform could retrieve a much richer representation.
Push metadata updates with WebHooks
Not every integration needs to continuously query an API.
ONIXEDIT Server also supports WebHooks.
When an ONIX product changes, ONIXEDIT Server can send a POST request to an endpoint in another system. The payload can be configured to contain only the information required by that application.
For example:
Supplier updates ONIX → ONIXEDIT Server processes the change → WebHook notifies your system → your database or storefront is updated
This enables event-driven integrations without repeatedly polling for changes.
Who can benefit from ONIX integration?
Publishers and content providers
Keep your existing title-management, ERP, or internal system while using ONIXEDIT Server to generate, validate, and distribute ONIX.
Distributors and aggregators
Automatically ingest ONIX from multiple providers, normalize it, and make the metadata available to your internal systems through the API. Our ONIXEDIT Server case study describes one such deployment.
Retailers and resellers
Integrate incoming ONIX metadata with e-commerce platforms, PIM systems, catalogues, or internal databases without implementing the complete ONIX standard internally. Read how Indigo selected ONIXEDIT Server to automate its ONIX metadata workflows.
Technology teams
Use standard REST API calls, JSON, XML, and WebHooks instead of developing and maintaining a complete ONIX processing engine inside every application.
You don’t have to build ONIX support from scratch
ONIX is a powerful standard, but its complexity shouldn’t have to propagate throughout your entire technology stack.
ONIXEDIT Server provides a dedicated ONIX layer that can receive metadata, automate processing, expose the information your applications need, and distribute updates to other systems.
Whether your integration starts with ONIX, ends with ONIX, or connects several metadata systems together, ONIXEDIT Server can become the bridge between them.
Key takeaways
-
Keep your systems: your ERP, PIM, in-house application, database or online store stays in place; ONIXEDIT Server adds the ONIX layer.
-
Both directions: generate ONIX from your own data, or ingest ONIX from partners and make it available to your applications.
-
Automated ingestion: the Automated Ingestion Agent processes ONIX 2.1, ONIX 3, ONIX 3.1, Excel, CSV and tab-delimited files as they arrive.
-
REST API and WebHooks: retrieve products as XML or JSON, request only the fields you need, and get notified when something changes.
-
For every link in the chain: publishers, distributors, aggregators, retailers, resellers and their technology teams.
Frequently asked questions
Can ONIXEDIT Server integrate with our existing ERP or PIM?
Yes. ONIXEDIT Server can be integrated with ERP, PIM, proprietary applications, internal databases, publishing systems, commerce platforms, and other systems that need to produce or consume ONIX metadata.
Can ONIXEDIT Server import ONIX from our suppliers?
Yes. Incoming ONIX files can be automatically ingested and their metadata can then be accessed by your own applications through the ONIXEDIT Server REST API.
Do our developers need to understand the complete ONIX standard?
Not necessarily. ONIXEDIT Server handles ONIX processing while your application can work with selected metadata exposed through XML or JSON.
Can ONIXEDIT notify our system when metadata changes?
Yes. WebHooks can send configurable payloads to your application’s endpoint when ONIX products are modified.
Ready to discuss your integration project?
Every integration is different.
Tell us what systems you need to connect and what metadata needs to move between them. We’ll help you determine the best ONIXEDIT Server architecture for your workflow.