# RELEX Solutions

> RELEX Solutions is a Helsinki-headquartered supply chain and retail planning software vendor.
> Its unified platform covers demand forecasting and sensing, inventory and replenishment,
> space and assortment, pricing and promotions, workforce and store operations, and integrated
> business planning for retailers, wholesalers and consumer goods manufacturers.

This file was GENERATED by API Evangelist from RELEX's public API surface. RELEX does not
publish an llms.txt of its own (https://www.relexsolutions.com/llms.txt returns 404).

## What RELEX exposes programmatically

RELEX publishes two OpenAPI 3.1 contracts, both as pre-rendered ReDoc reference pages. Neither
is served as a standalone .json or .yaml file — the spec is embedded in the page.

- RELEX Data API (91 operations across 83 paths, v4.28.3 for the published example customer).
  Near-real-time exchange of master data, transaction data, metadata and customer-specific
  custom resources between a customer's ERP/POS/WMS/MDM and the RELEX planning platform.
  Reference: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
  Production host pattern: https://{geography}.rest.relexsolutions.com/{customer}
  UAT host pattern:        https://uat-{geography}.rest.relexsolutions.com/{customer}
- RELEX Monitoring API (5 paths, v1.24.0). Read-only observability over a customer's own RELEX
  environments: file ingestion events, planning job events, environments, metrics.
  Reference: https://www.relexsolutions.com/api/monitoring-api-example-customer.html
  Hosts: https://eu.monitor.relexsolutions.com and https://us.monitor.relexsolutions.com

Other integration methods RELEX documents but does not expose as a public contract: a Batch API
over Azure Blob Storage (or SFTP), a bi-directional SAP Connector (S/4HANA on-prem, S/4HANA
private cloud/RISE, ECC 6.0 EHP8 — NOT S/4 public cloud/GROW), Managed Integration, and
Snowflake data sharing.

## The things an agent must know before calling

- THERE IS NO SELF-SERVICE ACCESS. Client ID, Client Secret and the RELEX Identity token endpoint
  are issued by RELEX during an implementation project. No trial, no free tier, no test key, no
  public sandbox, and the reference pages have no execute button.
- Auth is OAuth 2.0 Client Credentials against RELEX Identity (OpenID Connect). Send
  `Authorization: Bearer <jwt>`. No refresh token is issued — on 401, re-run the grant.
- HTTPS only. Plain HTTP fails with 400.
- An IP allowlist is usually in force; a 403 commonly means the caller's egress IP is not on it.
- WRITES ARE ASYNCHRONOUS. A 200 on a POST means the payload was ACCEPTED, not that it was
  processed. Ingestion errors appear later, and only at GET /meta/errors, queried by the
  request_id the write returned (or by a start/end timestamp window — the two modes are mutually
  exclusive). A single 2xx confirms nothing on its own.
- POST is an UPSERT and carries a LIST of records, not one record. POST and DELETE are both
  idempotent. Resending the same payload is safe. There is no Idempotency-Key header — reuse the
  same `meta.batch_id` (UUID) on every retry of the same logical request, and use a different one
  for every logically distinct request.
- Limits: 5 requests per second, 1 MB maximum request body. Over-rate returns 429, over-size
  returns 413, both as RFC 7807 application/problem+json. NO RateLimit-*, X-RateLimit-* or
  Retry-After headers are returned, so budget cannot be observed before it is spent. Response
  payloads are explicitly unlimited in size.
- Errors are RFC 7807 Problem Details with type/title/status (+detail). Type URIs look like
  https://relexsolutions.com/rest/errors/{status}. There is no numeric error-code registry.
- REVERSIBILITY IS LIMITED AND THIS MATTERS. Only 8 master-data resources have a DELETE
  (campaigns, delivery schedules, batch sizes, pre-pack variants, product replacements and
  references). NO transactional resource has a delete, void, cancel or reverse operation. A wrong
  transaction can only be corrected by overwriting it on its business key or by posting a
  compensating record. There is no dry-run or validate-only mode anywhere in the contract, and no
  reversal window is stated for anything.
- Records are keyed by BUSINESS keys, not surrogate ids — most commonly the composite of
  `product` + `location` (+ a date for time series). That is what makes POST an upsert. Only the
  four planning-output resources expose an {id} path parameter.
- Versioning is semver, but the public version number is the SUM of a shared Core version and a
  per-customer Data model version. Query it at GET /meta/version. Breaking changes ship behind a
  feature flag that defaults to the OLD behaviour, and the customer has 3 months before it flips.
  No Sunset or Deprecation headers are sent.

## Events

RELEX sends webhooks when planning OUTPUT data is ready — sales forecasts, order proposals,
workload driver forecasts. The payload is METADATA ONLY (id, resource, timestamp, relative url);
fetch the actual record with a follow-up GET. Delivery is via Svix with SVIX-ID, SVIX-TIMESTAMP
and SVIX-SIGNATURE (HMAC-SHA256) headers; verify the signature and disable CSRF on the receiving
endpoint. Success is any 2xx within 15 seconds; retries follow a published exponential schedule
(immediately, 5s, 5m, 30m, 2h, 5h, 10h, 10h). RELEX publishes no AsyncAPI document.

## What RELEX does NOT publish

- No client SDK in any language, on any registry. The only first-party client code is a Python
  code SAMPLE for the Monitoring API: https://github.com/relex/monitoring-api-demo
- No CLI, no Postman collection, no embeddable components.
- No public pricing, plans or quotas. /pricing/ redirects to a marketing article about RELEX's
  price-optimization product, not to RELEX's own prices.
- No public changelog or release notes.
- No /llms.txt, no /.well-known/security.txt, no /.well-known/api-catalog, and no A2A agent card
  on any RELEX host.
- No MCP endpoint. RELEX's integrations page claims native Model Context Protocol support and it
  markets 16 named planning agents, but no endpoint, package, tool list or agent card is published
  anywhere public, so no agent can reach it today.

## Reference

- Developer portal (GATED — Auth0 login required): https://docs.relexsolutions.com/
- Integrations overview: https://www.relexsolutions.com/integrations/
- Data API reference: https://www.relexsolutions.com/api/retail-restapi-example-customer.html
- Monitoring API: https://www.relexsolutions.com/relex-monitoring-api/
- Monitoring API reference: https://www.relexsolutions.com/api/monitoring-api-example-customer.html
- OpenID Connect discovery (EU, Data API authority):
  https://identity.prod-eu.prod.cc.relexsolutions.com/login/restapi_prod/.well-known/openid-configuration
- GitHub org: https://github.com/relex
- Security and compliance (ISO 27001:2013, SOC 2 / ISAE 3000 Type I+II, GDPR):
  https://www.relexsolutions.com/security-compliance/
- Vulnerability disclosure (security@relexsolutions.com, 90-day disclosure, safe harbour):
  https://www.relexsolutions.com/policy/vulnerability-disclosure/
- Trust center: https://www.relexsolutions.com/privacy-trust-center/
- Status page (PRIVATE — customer login required): https://status.relexsolutions.com/
- Support: https://www.relexsolutions.com/customer-support/
- Community portal: https://www.relexsolutions.com/community-portal/

Generated: 2026-08-26 by API Evangelist (https://apievangelist.com). Independent third-party
profile; not affiliated with or endorsed by RELEX Solutions.