How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
RELEX Solutions

RELEX Solutions Transactions API

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

Documentation Provider Profile APIs.io OpenAPI GitHub

RELEX Solutions Transactions API is one of 7 APIs that RELEX Solutions publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 27 operations across 27 paths, and defines 48 schemas. It is described by OpenAPI 3.2.0, at version v4.28.3.

Requests are made against 2 base URLs: https://uat-eu.rest.relexsolutions.com/restapi-test, https://eu.rest.relexsolutions.com/restapi-test.

27 operations 27 paths 48 schemas 8 GET19 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v4.28.3
Base URL
https://eu.rest.relexsolutions.com
Authentication
OAuth 2.0
Contact
support@relexsolutions.com
License
Apache 2.0
Resource Areas
1

Authentication & Security 1

RELEX Solutions Transactions API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • OAuth2 — The RELEX Data API uses OAuth 2 with the client credentials flow.

Paths & Operations 27

Across 27 paths, the API surfaces 27 operations — 8 GET, 19 POST. Each is listed below with its method, path, parameters, and response codes.

Transactions 27

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

POST
/data/transactions/adjustments
Adjustments
PostAdjustments 1 param body → 2004004014034044134295XX
POST
/data/transactions/balances
Balances
PostBalances 1 param body → 2004004014034044134295XX
POST
/data/transactions/batch_balances
Batch Balances
PostBatchBalances 1 param body → 2004004014034044134295XX
POST
/data/transactions/daily_sales
Daily Sales
PostDailySales 1 param body → 2004004014034044134295XX
POST
/data/transactions/dc_transactions
DC transactions
PostDcTransactions 1 param body → 2004004014034044134295XX
POST
/data/transactions/deliveries
Deliveries
PostDeliveries 1 param body → 2004004014034044134295XX
POST
/data/transactions/end_customer_transactions
End Customer Transactions
PostEndCustomerTransactions 1 param body → 2004004014034044134295XX
POST
/data/transactions/footfall_counts
Footfalls
PostFootfallCounts 1 param body → 2004004014034044134295XX
POST
/data/transactions/goods_received
Goods Received
PostGoodsReceived 1 param body → 2004004014034044134295XX
POST
/data/transactions/inventory_checks
Inventory Checks
PostInventoryChecks 1 param body → 2004004014034044134295XX
POST
/data/transactions/inventory_events
Inventory Events
PostInventoryEvents 1 param body → 2004004014034044134295XX
POST
/data/transactions/lost_sales
Lost Sales
PostLostSales 1 param body → 2004004014034044134295XX
POST
/data/transactions/open_purchase_orders
Open Purchase Orders
PostOpenPurchaseOrders 1 param body → 2004004014034044134295XX
POST
/data/transactions/open_sales_orders
Open Sales Orders
PostOpenSalesOrders 1 param body → 2004004014034044134295XX
POST
/data/transactions/orders
Orders
PostOrders 1 param body → 2004004014034044134295XX
POST
/data/transactions/sales
Sales
PostSales 1 param body → 2004004014034044134295XX
POST
/data/transactions/special_deliveries
Special Deliveries
PostSpecialDeliveries 1 param body → 2004004014034044134295XX
POST
/data/transactions/spoilages
Spoilages
PostSpoilages 1 param body → 2004004014034044134295XX
POST
/data/transactions/transfers
Transfers
PostTransfers 1 param body → 2004004014034044134295XX
GET
/data/transactions/sales_forecasts
Sales Forecasts List
list_GetSalesForecasts 1 param → 2004004014034044295XX
GET
/data/transactions/sales_forecasts/{id}
Sales Forecasts
get_GetSalesForecasts 1 param → 2004004014034044295XX
GET
/data/transactions/order_proposals
Order Proposals List
list_GetOrderProposals 1 param → 2004004014034044295XX
GET
/data/transactions/order_proposals/{id}
Order Proposals
get_GetOrderProposals 1 param → 2004004014034044295XX
GET
/data/transactions/workload_driver_forecasts_day
Workload Driver Forecasts Day List
list_GetWorkloadDriverForecastsDay 1 param → 2004004014034044295XX
GET
/data/transactions/workload_driver_forecasts_day/{id}
Workload Driver Forecasts Day
get_GetWorkloadDriverForecastsDay 1 param → 2004004014034044295XX
GET
/data/transactions/workload_driver_forecasts_quarter
Workload Driver Forecasts Quarter List
list_GetWorkloadDriverForecastsQuarter 1 param → 2004004014034044295XX
GET
/data/transactions/workload_driver_forecasts_quarter/{id}
Workload Driver Forecasts Quarter
get_GetWorkloadDriverForecastsQuarter 1 param → 2004004014034044295XX

Schemas 48

The contract defines 48 schemas that model the data the API accepts and returns. The most detailed are sale (30 properties), order (20 properties), open_purchase_order (16 properties), end_customer_transaction (15 properties). Each schema is shown below with its type and property counts.

retail_batch_balance_request_body
object
2 properties 1 required
order
object
20 properties 5 required
retail_order_request_body
object
2 properties 1 required
problem_details_400
object
Implementation of [RFC7807](https://tools.ietf.org/html/rfc7807) Problem Details object. Content type should always be application/problem+json. Problem type d…
6 properties 3 required
outbound_list_endpoint
object
2 properties
inbound_meta
object
2 properties
dc_transaction
object
9 properties 6 required
retail_spoilage_request_body
object
2 properties 1 required
balance
object
7 properties 5 required
retail_inventory_event_request_body
object
2 properties 1 required
open_sales_order
object
14 properties 6 required
inventory_check
object
13 properties 5 required
retail_footfall_count_request_body
object
2 properties 1 required
retail_lost_sale_request_body
object
2 properties 1 required
sale
object
30 properties 8 required
retail_workload_driver_forecasts_quarter
object
2 properties 2 required
lost_sale
object
14 properties 5 required
retail_daily_sale_request_body
object
2 properties 1 required
spoilage
object
9 properties 5 required
retail_delivery_request_body
object
2 properties 1 required
retail_transfer_request_body
object
2 properties 1 required
adjustment
object
13 properties 5 required
open_purchase_order
object
16 properties 6 required
problem_details_general
object
Implementation of [RFC7807](https://tools.ietf.org/html/rfc7807) Problem Details object. Content type should always be application/problem+json. Problem type d…
4 properties 3 required
goods_received
object
5 properties 2 required
end_customer_transaction
object
15 properties 5 required
delivery
object
14 properties 5 required
retail_dc_transaction_request_body
object
2 properties 1 required
special_delivery
object
12 properties 5 required
retail_workload_driver_forecasts_day
object
2 properties 2 required
retail_sales_forecasts
object
2 properties 2 required
accepted
object
2 properties 2 required
batch_balance
object
12 properties 6 required
retail_balance_request_body
object
2 properties 1 required
retail_open_sales_order_request_body
object
2 properties 1 required
retail_inventory_check_request_body
object
2 properties 1 required
retail_open_purchase_order_request_body
object
2 properties 1 required
time
stringnull
inventory_event
object
8 properties 2 required
retail_special_delivery_request_body
object
2 properties 1 required
transfer
object
14 properties 5 required
retail_adjustment_request_body
object
2 properties 1 required
footfall_count
object
4 properties 4 required
retail_end_customer_transaction_request_body
object
2 properties 1 required
retail_order_proposals
object
2 properties 2 required
daily_sale
object
7 properties 5 required
retail_goods_received_request_body
object
2 properties 1 required
retail_sale_request_body
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relex-transactions-api-openapi.yml Raw ↑

Other APIs RELEX Solutions publishes across the network.

RELEX Solutions Environments API
AE Profile APIs.io
RELEX Solutions Events API
AE Profile APIs.io
RELEX Solutions Health API
AE Profile APIs.io
RELEX Solutions Master data API
AE Profile APIs.io
RELEX Solutions Metadata API
AE Profile APIs.io
RELEX Solutions Metrics API
AE Profile APIs.io
#Transaction
← Back to R APIs
API Details
ID
relex:relex-transactions-api
Base URL
https://eu.rest.relexsolutions.com
Docs
https://www.relexsolutions.com/api/retail-restapi-example-customer.html
Provider
RELEX Solutions
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=relex-transactions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/relex-transactions-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of RELEX Solutions Transactions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.