RunRepeat Data access

RunRepeat Shoe Intelligence API

Enhance product pages and catalog workflows with scores, specs, measured lab results, and editorial content.

This is a read-only shoe-data API and bulk export for partners. The worked example uses one reviewed, published Shoe record.

  • Published sample
  • Weekly sync
  • Partners only
Request access
Published Shoe exampleOne record, four jobs

One record · four jobs

Use the same Shoe across the catalog.

Stable recordrr_shoe_41191Source: RunRepeat
1

Catalog match

Resolve the item you sell

1171927FLCK → HOKA Cielo X1 3.0
  • data.catalog_identifiers[].value
  • data.identity.name
Source: RunRepeat
2

Browse and filter

Place it in catalog views

road · competition · neutral
  • data.specs.running-surface
  • data.specs.running-pace
  • data.specs.running-arch-support
Source: RunRepeat
3

Product enrichment

Add reasons to keep reading

91/100 · Out-of-this-world shock absorption
  • data.scores.overall
  • data.editorial.pros[0]
Source: RunRepeat
4

Weekly reconciliation

Know what to refresh or remove

active · current · 2026-07-18T12:00:00Z
  • data.updated_at
  • data.status
  • data.availability

Use status and availability to decide what to refresh or remove during the weekly sync.

Source: RunRepeat
REST API or weekly bulk ingestionInspect sample

One reviewed Shoe makes the value concrete: a partner can turn licensed fields into a visible catalog or customer experience.

  • Online retailers and marketplaces
  • Brands with e-commerce platforms
  • Comparison sites and buying guides
  • Catalog and product-data teams

Use the fields your experience needs

A published Shoe can carry exact catalog identifiers, registered specifications, scores, lab measurements, and editorial assessment. Availability varies by the verified record and the partner's entitlement.

Match
Exact GTIN or brand-plus-SKU identifiers.
Describe
Registered specs and measured lab facts with definitions.
Assess
Overall and named suitability scores from the record.
Explain
Verdict, pros, and cons written by RunRepeat.

The two read paths are the REST API and the bulk export.

Choose request-time reads, weekly scheduled ingestion, or both for your integration.

Request-time read

REST API

Read an entitled Shoe or browse the entitled catalog through /api/v1.

Scheduled ingestion

Bulk export

Load the published dataset into your own catalog and reconcile weekly changes.

Access is arranged directly.

Tell us what you are building and which fields you need. RunRepeat will confirm whether the current partner dataset fits the job.

To request access, write to jens@runrepeat.com.

Request access

Jens Jakob Andersen
CEO, RunRepeat