RELEX Solutions website screenshot

RELEX Solutions

RELEX Solutions is a Helsinki-headquartered supply chain and retail planning software company whose unified platform covers demand forecasting, inventory and replenishment, space and assortment, pricing and promotions, workforce and store operations, and integrated business planning for retailers, wholesalers and consumer goods manufacturers. Its developer surface is deliberately narrow and integration-centric: customer data reaches the platform through the RELEX Data API (an OpenAPI 3.1 REST contract with 91 operations across master data, transactions, metadata and customer-specific custom resources), a Batch API over Azure Blob Storage or SFTP, a bi-directional SAP Connector, and Snowflake data sharing, while operational visibility is exposed through the RELEX Monitoring API for file and job events. Both APIs are secured with OAuth 2.0 client credentials against RELEX Identity, publish RFC 7807 problem responses, and are documented publicly as ReDoc reference pages, while the full RELEX Developer Portal at docs.relexsolutions.com sits behind an Auth0 login.

RELEX Solutions publishes 7 APIs on the APIs.io network, including Environments API, Events API, Health API, and 4 more. Tagged areas include Supply Chain, Retail, Demand Planning, Inventory Management, and Forecasting.

The RELEX Solutions catalog on APIs.io includes 1 event-driven AsyncAPI specification.

RELEX Solutions’ developer surface includes documentation, API reference, support, engineering blog, authentication, sandbox, and 31 more developer resources.

🌐 Visit website 📡 Source on GitHub
50.5/100 developing ▬ flat Agent 46/100 agent native Front door AI 5/6 prominent saas Full breakdown ↓
scored 2026-09-20 · rubric v0.22.0
AccessSelf serve
2 APIs
Supply ChainRetailDemand PlanningInventory ManagementForecastingPricingEnterprise SoftwareData IntegrationCompany

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Information & Data Management
BC-610
Master data
POST /data/master/assortments

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-20 · rubric v0.22.0
Composite quality — 50.5/100 · developing
Contract Quality 14.8 / 23
Developer Ergonomics 8.9 / 18
Access Clarity 6.6 / 18
Operational Transparency 7.7 / 12
Contract Governance 2.0 / 11
Discoverability 6.2 / 9
Create-or-Update Ergonomics 0.0 / 10
Agent readiness — 46/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 6 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/relex: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

RELEX Solutions Environments API

Endpoints for managing and retrieving customer-specific environment configurations.

RELEX Solutions Events API

Endpoints for fetching files and jobs event data.

RELEX Solutions Health API

Endpoint that report on the Monitoring API operational and readiness status.

RELEX Solutions Master data API

The namespace for master data contains the different endpoints for transferring master data.

RELEX Solutions Metadata API

The namespace for metadata contains the different endpoints for API metadata.

RELEX Solutions Metrics API

The Monitoring API exposes a Prometheus-compatible metrics endpoint at `/api/v1/{customer_id}/metrics`. The metrics available over this endpoint give quantitative insight into t...

RELEX Solutions Transactions API

The namespace for transaction data contains the different endpoints for inventory transactions, balance and open order information.

Scroll for all 7

Pricing Plans 1

Published pricing tiers and plan structures.

Relex Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Relex Rate Limits

2 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Relex Data Api Webhooks

ASYNCAPI

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Relex Authentication

oauth2 · 2 schemes

SECURITY

Relex Domain Security

TLSv1.3 · DMARC

SECURITY

Relex Vulnerability Disclosure

contact published

SECURITY

Relex Trust Center

ISO/IEC 27001:2013, SOC 2 (ISAE 3000), GDPR

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Relex Scopes

51 scopes

51 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 Sandbox
Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference
 OpenAPI
OpenAPI

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown
WellKnown
 AgentSkill
AgentSkill
 LLMsTxt
LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Idempotency
Idempotency
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 Conformance
Conformance
 DataModel
DataModel
 Webhooks
Webhooks

Scroll for all 7

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages

Access & Security 7

Authentication, authorization, and security posture

TrustCenter
TrustCenter
 VulnerabilityDisclosure
VulnerabilityDisclosure
 DomainSecurity
DomainSecurity
 Compliance
Compliance
 Security
Security
 Authentication
Authentication
 OAuthScopes
OAuthScopes

Scroll for all 7

Operate 5

Status, limits, changes, and where to get help

Support
Support
 HelpCenter
HelpCenter
 StatusPage
StatusPage
 Deprecation
Deprecation
 RateLimits
RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Plans
Plans

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Other 3

Properties that don't map to a standard resource type

CapabilityMap
CapabilityMap
 Overlay
Overlay
 Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
aid: relex
name: RELEX Solutions
description: 'RELEX Solutions is a Helsinki-headquartered supply chain and retail planning software company whose unified
  platform covers demand forecasting, inventory and replenishment, space and assortment, pricing and promotions, workforce
  and store operations, and integrated business planning for retailers, wholesalers and consumer goods manufacturers. Its
  developer surface is deliberately narrow and integration-centric: customer data reaches the platform through the RELEX Data
  API (an OpenAPI 3.1 REST contract with 91 operations across master data, transactions, metadata and customer-specific custom
  resources), a Batch API over Azure Blob Storage or SFTP, a bi-directional SAP Connector, and Snowflake data sharing, while
  operational visibility is exposed through the RELEX Monitoring API for file and job events. Both APIs are secured with OAuth
  2.0 client credentials against RELEX Identity, publish RFC 7807 problem responses, and are documented publicly as ReDoc
  reference pages, while the full RELEX Developer Portal at docs.relexsolutions.com sits behind an Auth0 login.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-09-02'
  method: derived
image: https://s32519.pcdn.co/wp-content/uploads/2024/01/RELEX-logo-1200x627-social.png
url: https://raw.githubusercontent.com/api-evangelist/relex/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-09-16'
tags:
- Supply Chain
- Retail
- Demand Planning
- Inventory Management
- Forecasting
- Pricing
- Enterprise Software
- Data Integration
- Company
apis:
- aid: relex:relex-environments-api
  name: RELEX Solutions Environments API
  description: Endpoints for managing and retrieving customer-specific environment configurations.
  humanURL: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  baseURL: https://eu.rest.relexsolutions.com
  tags:
  - Environment
  tags_raw:
  - Environments
  properties:
  - type: OpenAPI
    url: openapi/relex-environments-api-openapi.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  - type: Webhooks
    url: asyncapi/relex-data-api-webhooks.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/monitoring-api-example-customer.html
  - type: SourceCode
    url: https://github.com/relex/monitoring-api-demo
- aid: relex:relex-events-api
  name: RELEX Solutions Events API
  description: Endpoints for fetching files and jobs event data.
  humanURL: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  baseURL: https://eu.rest.relexsolutions.com
  tags:
  - Event
  tags_raw:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/relex-events-api-openapi.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  - type: Webhooks
    url: asyncapi/relex-data-api-webhooks.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/monitoring-api-example-customer.html
  - type: SourceCode
    url: https://github.com/relex/monitoring-api-demo
- aid: relex:relex-health-api
  name: RELEX Solutions Health API
  description: Endpoint that report on the Monitoring API operational and readiness status.
  humanURL: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  baseURL: https://eu.rest.relexsolutions.com
  tags:
  - Health
  properties:
  - type: OpenAPI
    url: openapi/relex-health-api-openapi.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  - type: Webhooks
    url: asyncapi/relex-data-api-webhooks.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/monitoring-api-example-customer.html
  - type: SourceCode
    url: https://github.com/relex/monitoring-api-demo
- aid: relex:relex-master-data-api
  name: RELEX Solutions Master data API
  description: The namespace for master data contains the different endpoints for transferring master data.
  humanURL: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  baseURL: https://eu.rest.relexsolutions.com
  tags:
  - Master Data
  tags_raw:
  - Master data
  properties:
  - type: OpenAPI
    url: openapi/relex-master-data-api-openapi.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  - type: Webhooks
    url: asyncapi/relex-data-api-webhooks.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/monitoring-api-example-customer.html
  - type: SourceCode
    url: https://github.com/relex/monitoring-api-demo
- aid: relex:relex-metadata-api
  name: RELEX Solutions Metadata API
  description: The namespace for metadata contains the different endpoints for API metadata.
  humanURL: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  baseURL: https://eu.rest.relexsolutions.com
  tags:
  - Metadata
  properties:
  - type: OpenAPI
    url: openapi/relex-metadata-api-openapi.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  - type: Webhooks
    url: asyncapi/relex-data-api-webhooks.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/monitoring-api-example-customer.html
  - type: SourceCode
    url: https://github.com/relex/monitoring-api-demo
- aid: relex:relex-metrics-api
  name: RELEX Solutions Metrics API
  description: "The Monitoring API exposes a Prometheus-compatible metrics endpoint at `/api/v1/{customer_id}/metrics`.\n\
    The metrics available over this endpoint give quantitative insight into the throughput,\nlatency, and reliability of data\
    \ flowing into RELEX services.\n\nWhen applicable, metrics are labelled with a `type` dimension that identifies the data\
    \ type\n(e.g. `sales`, `product_locations`). The `type` values are normalised to use underscores.\n\n## Plan data ingestion\
    \ metrics\n\nThese metrics describe the end-to-end data ingestion pipeline from the point data\nis received by RELEX until\
    \ it is consumed by RELEX Plan, the core supply chain\nplanning application. The metrics are technology-agnostic and apply\
    \ regardless of\nwhether data is ingested via batch file uploads or via the Data API.\n\n| Metric | Type | Unit | Description\
    \ |\n|--------|------|------|-------------|\n| `plan_data_ingestion_delay_seconds` | Gauge | seconds | End-to-end latency\
    \ of RELEX Plan data ingestion, measured as the delay between data being sent to RELEX and data being consumed by RELEX\
    \ Plan. |\n| `plan_data_ingestion_messages_total` | Counter | messages | Total number of messages (files or records) ingested\
    \ by RELEX Plan. Tracks overall ingestion throughput. |\n| `plan_data_ingestion_rows_total` | Counter | rows | Total number\
    \ of data rows processed by RELEX Plan during ingestion. Provides a fine-grained view of data volume beyond message counts.\
    \ |\n\n  Labels used with `plan_data_ingestion_*` metrics:\n\n  | Label | Meaning |\n  |-------|---------|\n  | `app`\
    \ | Which customer application the metric belongs to. |\n  | `env` | Which customer environment the application belongs\
    \ to. |\n  | `type` | Which kind of integration data stream the metric describes. |\n\n## Data API HTTP metrics\n\nThese\
    \ metrics follow [OpenTelemetry semantic conventions](https://opentelemetry.io/docs/specs/semconv/http/http-metrics/)\n\
    and describe the HTTP layer of the [RELEX Data API](https://docs.relexsolutions.com/docs/restapis/data-api/guide),\nfor\
    \ customers using that integration method.\n\n| Metric | Type | Unit | Description |\n|--------|------|------|-------------|\n\
    | `http_server_request_duration_ms` | Histogram | milliseconds | Duration of HTTP requests received by the Data API. |\n\
    | `http_server_request_body_size_bytes` | Counter | bytes | Cumulative size of HTTP request bodies received by the Data\
    \ API. Indicates the volume of data being sent to RELEX. |\n| `http_server_response_body_size_bytes` | Counter | bytes\
    \ | Cumulative size of HTTP response bodies returned by the Data API. |\n| `http_server_request_count_by_status` | Counter\
    \ | requests | Total number of HTTP requests received by the Data API, broken down by HTTP status code (`http_status`\
    \ label). |\n\nLabels used with `http_server_request_duration_ms*` metrics:\n\n| Label | Meaning |\n|-------|---------|\n\
    | `type` | Which kind of integration data stream the metric describes. |\n| `http_path` | Which API endpoint received\
    \ the data in RELEX. |\n| `le` | For bucket metrics, the upper time limit of the bucket in milliseconds. This label is\
    \ not present on the related `_sum` and `_count` metrics. |\n\nLabels used with `http_server_request_count_by_status`:\n\
    \n| Label | Meaning |\n|-------|---------|\n| `type` | Which kind of integration data stream the metric describes. |\n\
    | `http_path` | Which API endpoint received the data in RELEX. |\n| `http_status` | Which HTTP response status RELEX returned,\
    \ for example `200` or `400`. |\n\nLabels used with `http_server_request_body_size_bytes*` and `http_server_response_body_size_bytes*`\
    \ metrics:\n\n| Label | Meaning |\n|-------|---------|\n| `type` | Which kind of integration data stream the metric describes.\
    \ |\n| `http_path` | Which API endpoint received the data in RELEX for request size metrics, or which API endpoint RELEX\
    \ sent the data from for response size metrics. |"
  humanURL: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  baseURL: https://eu.rest.relexsolutions.com
  tags:
  - Metrics
  properties:
  - type: OpenAPI
    url: openapi/relex-metrics-api-openapi.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  - type: Webhooks
    url: asyncapi/relex-data-api-webhooks.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/monitoring-api-example-customer.html
  - type: SourceCode
    url: https://github.com/relex/monitoring-api-demo
- aid: relex:relex-transactions-api
  name: RELEX Solutions Transactions API
  description: The namespace for transaction data contains the different endpoints for inventory transactions, balance and
    open order information.
  humanURL: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  baseURL: https://eu.rest.relexsolutions.com
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/relex-transactions-api-openapi.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  - type: Webhooks
    url: asyncapi/relex-data-api-webhooks.yml
  - type: Documentation
    url: https://www.relexsolutions.com/api/monitoring-api-example-customer.html
  - type: SourceCode
    url: https://github.com/relex/monitoring-api-demo
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/relex-capability-edges.yml
  name: RELEX Solutions Business Capability Map
- type: Overlay
  url: overlays/relex-data-api-overlay.yaml
- type: Overlay
  url: overlays/relex-monitoring-api-overlay.yaml
- type: TrustCenter
  url: security/relex-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/relex-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/relex-domain-security.yml
- type: Website
  url: https://www.relexsolutions.com/
- type: DeveloperPortal
  url: https://docs.relexsolutions.com/
- type: Documentation
  url: https://www.relexsolutions.com/integrations/
- type: APIReference
  url: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
- type: Support
  url: https://www.relexsolutions.com/customer-support/
- type: HelpCenter
  url: https://www.relexsolutions.com/community-portal/
- type: Blog
  url: https://www.relexsolutions.com/careers/blog/
- type: GitHubOrganization
  url: https://github.com/relex
- type: TermsOfService
  url: https://www.relexsolutions.com/policy/terms-of-use-website/
- type: PrivacyPolicy
  url: https://www.relexsolutions.com/policy/privacy-policy-relex-website/
- type: Compliance
  url: https://www.relexsolutions.com/security-compliance/
- type: Security
  url: https://www.relexsolutions.com/policy/vulnerability-disclosure/
- type: StatusPage
  url: https://status.relexsolutions.com/
- type: OpenAPI
  url: openapi/_original/relex-data-api-openapi.json
- type: Authentication
  url: authentication/relex-authentication.yml
- type: OAuthScopes
  url: scopes/relex-scopes.yml
- type: WellKnown
  url: well-known/relex-well-known.yml
- type: Conventions
  url: conventions/relex-conventions.yml
- type: Idempotency
  url: conventions/relex-conventions.yml
- type: ErrorCatalog
  url: errors/relex-problem-types.yml
- type: Lifecycle
  url: lifecycle/relex-lifecycle.yml
- type: Deprecation
  url: lifecycle/relex-lifecycle.yml
- type: RateLimits
  url: rate-limits/relex-rate-limits.yml
- type: Plans
  url: plans/relex-plans-pricing.yml
- type: Conformance
  url: conformance/relex-conformance.yml
- type: DataModel
  url: data-model/relex-data-model.yml
- type: Sandbox
  url: sandbox/relex-sandbox.yml
- type: Webhooks
  url: asyncapi/relex-data-api-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/relex-llms.txt
- type: Packages
  url: packages/relex-packages.yml
x-enrichment:
  date: '2026-08-26'
  status: enriched
  artifacts_added: 31
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/relex"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/relex/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/relex/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.