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 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-08-26' 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: - 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`. The metrics available over this endpoint give quantitative insight into the throughput, latency, and reliability of data flowing into RELEX services. When applicable, metrics are labelled with a `type` dimension that identifies the data type (e.g. `sales`, `product_locations`). The `type` values are normalised to use underscores. ## Plan data ingestion metrics These metrics describe the end-to-end data ingestion pipeline from the point data is received by RELEX until it is consumed by RELEX Plan, the core supply chain planning application. The metrics are technology-agnostic and apply regardless of whether data is ingested via batch file uploads or via the Data API. | Metric | Type | Unit | Description | |--------|------|------|-------------| | `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. | | `plan_data_ingestion_messages_total` | Counter | messages | Total number of messages (files or records) ingested by RELEX Plan. Tracks overall ingestion throughput. | | `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. | Labels used with `plan_data_ingestion_*` metrics: | Label | Meaning | |-------|---------| | `app` | Which customer application the metric belongs to. | | `env` | Which customer environment the application belongs to. | | `type` | Which kind of integration data stream the metric describes. | ## Data API HTTP metrics These metrics follow [OpenTelemetry semantic conventions](https://opentelemetry.io/docs/specs/semconv/http/http-metrics/) and describe the HTTP layer of the [RELEX Data API](https://docs.relexsolutions.com/docs/restapis/data-api/guide), for customers using that integration method. | Metric | Type | Unit | Description | |--------|------|------|-------------| | `http_server_request_duration_ms` | Histogram | milliseconds | Duration of HTTP requests received by the Data API. | | `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. | | `http_server_response_body_size_bytes` | Counter | bytes | Cumulative size of HTTP response bodies returned by the Data API. | | `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). | Labels used with `http_server_request_duration_ms*` metrics: | Label | Meaning | |-------|---------| | `type` | Which kind of integration data stream the metric describes. | | `http_path` | Which API endpoint received the data in RELEX. | | `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. | Labels used with `http_server_request_count_by_status`: | Label | Meaning | |-------|---------| | `type` | Which kind of integration data stream the metric describes. | | `http_path` | Which API endpoint received the data in RELEX. | | `http_status` | Which HTTP response status RELEX returned, for example `200` or `400`. | Labels used with `http_server_request_body_size_bytes*` and `http_server_response_body_size_bytes*` metrics: | Label | Meaning | |-------|---------| | `type` | Which kind of integration data stream the metric describes. | | `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/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