Skip to content

NEWUnify Agents (MCP): governed AI access to finance data. Early access.See Unify Agents

IR

PIM INTEGRATION

inriver integration with the Unify Catalog API

Planned: inriver products, items and fields, plus 3 more objects, on one data model.

RoadmapAPI key · Sandbox yes

GET /v1/product-data/products?platform=inriver&limit=1

API design preview

Request

curl "https://api.unifyint.com/v1/product-data/products?platform=inriver&limit=1" \
  -H "Authorization: Bearer $UNIFY_API_KEY"

200 OK · API design preview

{
  "data": [
    {
      "id": "pro_01EXAMPLE",
      "object": "product",
      "remote_id": "example-1001",
      "name": "Example product",
      "sku": "SKU-1001",
      "quantity": 24,
      "updated_at": "2026-10-28T14:02:11Z",
      "raw": { "...": "original inriver record, unchanged" }
    }
  ],
  "next_cursor": null
}

API design preview. Field names may change before general availability.

On our roadmap. Request it to move it up.

Request inriver

About the inriver integration

inriver is a product information management platform for manufacturers, distributors and brands with complex catalogs. The Unify Catalog API reads its entities, fields, categories, resources and channels.

inriver's REST API uses API keys per environment, with an entity-and-link model that each customer configures. The Unify Catalog API maps product, item, category and resource entities, their fields and channel structures to the Unify Graph.

Status
Roadmap
Category
PIM
Auth
API key
Sandbox
Available
Webhooks
No (polling)
Bank feeds
No
Regions
EU, US, UK

Supported objects

Read and write status for each inriver object in the Unify Catalog API. Write appears only where write-back is confirmed.

  • Products

    Read on roadmapWrite on roadmap
  • Items

    Read on roadmapWrite on roadmap
  • Fields

    Read on roadmap
  • Categories

    Read on roadmapWrite on roadmap
  • Assets

    Read on roadmapWrite on roadmap
  • Channels

    Read on roadmap

Why build inriver on Unify Int

  • One data model

    inriver records arrive in the same Unify Graph shape as every other platform in the category, with the original record kept in raw.

  • Unify Connect

    A white-label flow for your customers to authorize inriver. Tokens are stored and refreshed for you.

  • Custom fields and passthrough

    Map inriver custom fields per connection, and call any endpoint the model does not cover through passthrough requests.

  • Unify Monitor

    Request logs, sync health and alerts for every inriver connection, so support can see what happened.

inriver integration questions

Does Unify Int support inriver products and fields?
inriver is on the Unify Int roadmap. The planned scope covers reading products, items, fields, categories, assets and channels, with write-back for products, items and categories to follow. Request it to move it up, or ask the Technology Center about a custom build.
How do customers connect their inriver account?
Your customer creates a REST API key in the inriver Control Center and enters it in Unify Connect.
Is there a inriver sandbox for testing?
Yes. inriver customers have test environments that can be connected before production.
How often does inriver data sync?
inriver does not emit webhooks for most objects, so Unify Sync polls incrementally on the schedule you set per object, typically every 15 minutes to daily, and sends you signed webhooks when records change.
Can I access inriver custom fields?
inriver field types and entity models are customer-defined; Unify Int maps them per connection to the core product fields.

Get started

Connect once. Build everything else on top.

Request sandbox access, or book 30 minutes with an engineer to map your integrations.

Free sandbox access. No credit card. Reply within one business day.