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
SAP S/4HANA

SAP S/4HANA Sales Orders API

Operations on sales order header records

Provider Profile APIs.io OpenAPI GitHub

SAP S/4HANA Sales Orders API is one of 6 APIs that SAP S/4HANA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 19 JSON Schema definitions.

Tagged areas include Sales Orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, a JSON-LD context, and 19 JSON Schemas.

This API exposes 5 operations across 2 paths, and defines 13 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 2 base URLs: https://sandbox.api.sap.com/s4hanacloud/sap/opu/odata/sap/API_SALES_ORDER_SRV, https://{host}:{port}/sap/opu/odata/sap/API_SALES_ORDER_SRV.

5 operations 2 paths 13 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Servers
https://sandbox.api.sap.com/s4hanacloud/sap/opu/odata/sap/API_SALES_ORDER_SRV
https://{host}:{port}/sap/opu/odata/sap/API_SALES_ORDER_SRV
Authentication
HTTP Basic, OAuth 2.0
Contact
SAP API Support
License
SAP Developer License
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

SAP S/4HANA Sales Orders API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It supports OAuth 2.0 (oauth2) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • basicAuth — Basic authentication using SAP user credentials
  • oauth2 — OAuth 2.0 authentication for SAP S/4HANA Cloud

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Sales Orders 5

Operations on sales order header records

GET
/A_SalesOrder
Sap S/4hana Retrieve a List of Sales Orders
listSalesOrders 7 params → 200401403
POST
/A_SalesOrder
Sap S/4hana Create a New Sales Order
createSalesOrder body → 201400401403
GET
/A_SalesOrder('{SalesOrder}')
Sap S/4hana Retrieve a Single Sales Order by Key
getSalesOrder 3 params → 200401403404
PATCH
/A_SalesOrder('{SalesOrder}')
Sap S/4hana Update a Sales Order Header
updateSalesOrder 2 params body → 204400401404412
DELETE
/A_SalesOrder('{SalesOrder}')
Sap S/4hana Delete a Sales Order
deleteSalesOrder 2 params → 204401404412

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are SalesOrder (59 properties), SalesOrderItem (55 properties), SalesOrderHeaderPrcgElmnt (29 properties), SalesOrderCreate (20 properties). Each schema is shown below with its type and property counts.

ODataError
object
OData error response envelope
1 property
SalesOrderItemCreate
object
Request payload for creating a new sales order item
20 properties
SalesOrderText
object
Sales order header text entity (ASalesOrderText) for long texts associated with the sales order header.
4 properties
SalesOrderUpdate
object
Request payload for updating sales order header fields
11 properties
SalesOrder
object
Sales order header entity (ASalesOrder) representing a complete sales document in SAP S/4HANA. Contains organizational data, customer references, pricing total…
59 properties
SalesOrderItemPrcgElmnt
object
Sales order item pricing element entity (ASalesOrderItemPrcgElmnt) representing a pricing condition at the item level.
19 properties
SalesOrderItemText
object
Sales order item text entity (ASalesOrderItemText) for long texts associated with a sales order item.
5 properties
SalesOrderItemPartner
object
Sales order item partner entity (ASalesOrderItemPartner) representing a business partner in a specific function role at the item level.
5 properties
SalesOrderScheduleLine
object
Sales order schedule line entity (ASalesOrderScheduleLine) representing a delivery schedule for a sales order item with confirmed quantities and dates from ava…
13 properties
SalesOrderHeaderPartner
object
Sales order header partner entity (ASalesOrderHeaderPartner) representing a business partner in a specific partner function role at the header level.
6 properties
SalesOrderCreate
object
Request payload for creating a new sales order with optional deep insert
20 properties 4 required
SalesOrderItem
object
Sales order item entity (ASalesOrderItem) representing a line item in a sales order. Contains material, quantity, pricing, plant assignment, and item-level pro…
55 properties
SalesOrderHeaderPrcgElmnt
object
Sales order header pricing element entity (ASalesOrderHeaderPrcgElmnt) representing a pricing condition at the header level, such as overall discounts, surchar…
29 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sap-s4hana-sales-orders-api-openapi.yml Raw ↑

Other APIs SAP S/4HANA publishes across the network.

SAP S/4HANA Partners API
AE Profile APIs.io
SAP S/4HANA Pricing Elements API
AE Profile APIs.io
SAP S/4HANA Sales Order Items API
AE Profile APIs.io
SAP S/4HANA Schedule Lines API
AE Profile APIs.io
SAP S/4HANA Text API
AE Profile APIs.io
#Sales Orders
← Back to S APIs
API Details
ID
sap-s4hana:sap-s4hana-sales-orders-api
Server
https://sandbox.api.sap.com/s4hanacloud/sap/opu/odata/sap/API_SALES_ORDER_SRV
Provider
SAP S/4HANA
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=sap-s4hana-sales-orders-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/sap-s4hana-sales-orders-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 SAP S/4HANA Sales Orders 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.