1WorldSync Content1 API

Name: 1WorldSync Content1 API API
Brand: 1WorldSync Content1 API
Availability: InStock

★ Only Publicly Available SpecE CommerceStorefrontnone2 EndpointsREST

For Agents

Search and retrieve trusted brand-supplied product content from the 1WorldSync network through two endpoints — list products and fetch a single product by reference ID.

Quickstart

Get started with 1WorldSync Content1 API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"fetch a 1WorldSync product record"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with 1WorldSync Content1 API API.

Search the 1WorldSync product catalogue with /products including filters and pagination parameters

Retrieve a single product's full content payload via /products/{itemReferenceId}

Pull brand-supplied descriptions, attributes, marketing copy, and digital asset references for a product

Resolve a GTIN, UPC, or internal item reference to authoritative manufacturer content

GET STARTED

Start building with 1WorldSync Content1 API API

Explore with Jentic

View OpenAPI Spec

Use for: Search 1WorldSync for products matching a brand or category, Retrieve the full product content record for a given item reference ID, Pull localised product descriptions for a SKU before publishing to a regional storefront, Get the official digital asset list for a SKU including hero images and instruction sheets

Not supported: Does not handle order processing, inventory levels, pricing, or storefront management — use for retrieving brand-supplied product content from the 1WorldSync network only.

Jentic publishes the only available OpenAPI specification for 1WorldSync Content1 API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for 1WorldSync Content1 API, keeping it validated and agent-ready. 1WorldSync Content1 provides retailer-grade product content sourced directly from brand owners through 1WorldSync's product information network. The two endpoints expose a product search at /products and a single-product detail lookup at /products/{itemReferenceId}. Typical responses include identifiers (GTIN, UPC), localised descriptions, attributes, marketing copy, and digital assets. The API is positioned for retailers, marketplaces, and product information management (PIM) systems that need authoritative manufacturer-supplied product content.

Use Cases

Patterns agents use 1WorldSync Content1 API API for, with concrete tasks.

★ Retailer Catalogue Backfill

Retailers and marketplaces call /products on a schedule to pull batches of newly onboarded SKUs and /products/{itemReferenceId} for the full content payload of each one. The brand-supplied descriptions, attributes, and digital assets land directly in the retailer's PIM and replace lower-quality data scraped from supplier feeds. A first integration takes a few days including pagination and PIM mapping.

Page through /products filtered to a target brand, then call /products/{itemReferenceId} for each result and write the response to the retailer's PIM staging table.

Product Detail Page Enrichment

E-commerce platforms call /products/{itemReferenceId} to enrich a product detail page with authoritative manufacturer copy, structured attributes, and digital assets. Because the content originates with the brand owner it improves discoverability and conversion versus scraped or supplier-supplied descriptions. Typical wiring is half a day behind a CMS template.

Call /products/{itemReferenceId} with the SKU's reference ID and return the localised description, marketing copy, and the first three image asset URLs.

Marketplace Onboarding Validation

Marketplace onboarding pipelines call /products to confirm that a seller-supplied SKU exists in the 1WorldSync network and /products/{itemReferenceId} to compare the seller's submitted attributes against the brand owner's authoritative record. Discrepancies are flagged for the seller to correct before listing goes live, which reduces returns and listing-quality complaints.

Search /products for a candidate GTIN, fetch /products/{itemReferenceId} for the matching record, and return any attribute where the seller's submission differs from the master.

Digital Asset Sync

Digital asset management (DAM) tools call /products/{itemReferenceId} to pull the brand owner's official image, video, and document links and mirror them into the retailer's CDN. This keeps creative assets aligned with the brand's latest packaging and marketing without manual asset uploads.

Call /products/{itemReferenceId} for a list of SKUs and return only the digital asset URLs grouped by asset type (image, video, document).

AI Agent Catalogue Operations

An AI agent embedded in a retailer's catalogue operations team calls 1WorldSync Content1 through Jentic to look up master records, refresh stale content, and backfill new SKUs without bespoke client code. Jentic exposes both endpoints as typed tools with discoverable input schemas so the agent picks /products vs /products/{itemReferenceId} based on whether it is searching or fetching.

Search Jentic for 'fetch a 1WorldSync product record', load the schema for /products/{itemReferenceId}, and execute the call for the SKU's reference ID supplied by the user.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for 1worldsync content1 api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/products

Search the 1WorldSync product catalogue

GET

/products/{itemReferenceId}

Fetch a single product record

GET

/products

Search the 1WorldSync product catalogue

GET

/products/{itemReferenceId}

Fetch a single product record

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Customer-issued 1WorldSync credentials are stored encrypted in the Jentic vault (MAXsystem) and applied at execution time. Because the spec does not declare a security scheme, the actual credential pattern is configured per Jentic deployment based on the customer's 1WorldSync contract.

Intent-based discovery

Agents search Jentic by intent (e.g. 'fetch a 1WorldSync product record' or 'search 1WorldSync products') and Jentic returns the two Content1 operations with their input schemas, so the agent does not need to read 1WorldSync portal docs.

Time to first call

Direct integration: a few days including credential setup, pagination, and PIM mapping. Through Jentic: under an hour from search to first successful call once the customer credentials are loaded into the vault.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Shopify

Shopify is the storefront and order layer that consumes the brand-grade product content sourced from 1WorldSync.

Use 1WorldSync to pull authoritative product content and call Shopify's product endpoints to upsert that content onto the storefront.

Complementary

eBay

eBay's listing APIs consume product content; 1WorldSync supplies the brand-supplied master record behind the listing.

Use 1WorldSync to fetch a master content record and call eBay's listing API to publish it to a marketplace listing.

Alternative

Best Buy

Best Buy's API exposes a single retailer's product catalogue; 1WorldSync exposes brand-supplied master content across many retailers.

Choose Best Buy when only Best Buy's catalogue is needed. Choose 1WorldSync when the retailer needs manufacturer-grade master content portable across stores.

Alternative

Edamam Food and Recipe

Edamam covers grocery and recipe metadata; 1WorldSync covers a far broader brand-supplied product catalogue.

Choose Edamam when the workload is grocery and nutrition specific. Stay with 1WorldSync when manufacturer-grade content is needed across non-food categories.

FAQs

Specific to using 1WorldSync Content1 API API through Jentic.

Why is there no official OpenAPI spec for 1WorldSync Content1 API?

1WorldSync does not publish an OpenAPI specification on its public marketing site. Jentic generates and maintains this spec so that AI agents and developers can call 1WorldSync Content1 API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the 1WorldSync Content1 API use?

The published spec does not declare a security scheme. In practice 1WorldSync issues per-customer credentials at contract signing and access is controlled at the network level; refer to your 1WorldSync onboarding pack for the exact credential pattern your account uses.

Can I retrieve a single product's full content record?

Yes. GET /products/{itemReferenceId} returns the full content payload for one product including identifiers, attributes, localised descriptions, and digital asset references. Use GET /products to discover the item reference IDs first.

What are the rate limits for the 1WorldSync Content1 API?

Rate limits are negotiated per customer contract rather than published in the spec. Production callers should batch search calls and cache /products/{itemReferenceId} responses for the typical content refresh interval agreed with 1WorldSync.

How do I backfill a retailer PIM through Jentic?

Run `pip install jentic`, search for 'list 1WorldSync products' and 'fetch a 1WorldSync product record', and chain the two operations: page through GET /products and call GET /products/{itemReferenceId} for each hit. Jentic loads the input schema for each endpoint.

Does 1WorldSync return localised product descriptions?

Yes. The /products/{itemReferenceId} response carries localised marketing copy and descriptions when the brand owner has supplied them, which is how retailers populate region-specific storefronts from a single source of truth.