SAP S/4HANA
Collection of SAP S/4HANA Cloud and On-Premise APIs for enterprise resource planning.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles SAP S/4HANA the way a machine reads it — 89 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — SAP S/4HANA scores 59.3/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile SAP S/4HANA
Each block below is one kind of artifact we hold for SAP S/4HANA. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SAP S/4HANA Partners API
Operations on header and item partner functions
SAP S/4HANA Pricing Elements API
Operations on header and item pricing elements
SAP S/4HANA Sales Order Items API
Operations on sales order line items
SAP S/4HANA Sales Orders API
Operations on sales order header records
SAP S/4HANA Schedule Lines API
Operations on item schedule lines for delivery scheduling
SAP S/4HANA Text API
Operations on header and item text records
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
SAP S/4HANA Sales Order API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Sap S4Hana Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Sap S4Hana Finops
FINOPSFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
OData V2 and V4 APIs
RESTful APIs following OData protocol for standardized CRUD operations and query capabilities.
Deep Insert
Create complex documents with header and dependent entities in a single API request.
Optimistic Concurrency
ETag-based concurrency control to prevent conflicting updates to business documents.
Real-Time Integration
Synchronous API access to live ERP data for real-time business process integration.
Multi-Module Coverage
APIs spanning finance, sales, procurement, logistics, manufacturing, and HR modules.
Semantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Sap S4Hana Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
SAP S/4HANA API Rules
SPECTRALSAP S/4HANA API Rules
SPECTRALJSON Schema 29
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ODataError
JSON SCHEMAODataError
JSON SCHEMASalesOrderCreate
JSON SCHEMASalesOrderHeaderPartner
JSON SCHEMASalesOrderHeaderPrcgElmnt
JSON SCHEMASalesOrderItemCreate
JSON SCHEMASalesOrderItemPartner
JSON SCHEMASalesOrderItemPrcgElmnt
JSON SCHEMASalesOrderItem
JSON SCHEMASalesOrderItemText
JSON SCHEMASalesOrderItemUpdate
JSON SCHEMASalesOrderScheduleLine
JSON SCHEMASalesOrder
JSON SCHEMASalesOrderText
JSON SCHEMASalesOrderUpdate
JSON SCHEMASAP S/4HANA Sales Order
JSON SCHEMASalesOrder
JSON SCHEMASalesOrderCreate
JSON SCHEMASalesOrderHeaderPartner
JSON SCHEMASalesOrderHeaderPrcgElmnt
JSON SCHEMASalesOrderItem
JSON SCHEMASalesOrderItemCreate
JSON SCHEMASalesOrderItemPartner
JSON SCHEMASalesOrderItemPrcgElmnt
JSON SCHEMASalesOrderItemText
JSON SCHEMASalesOrderItemUpdate
JSON SCHEMASalesOrderScheduleLine
JSON SCHEMASalesOrderText
JSON SCHEMASalesOrderUpdate
JSON SCHEMAScroll within the panel for all 29 ·
JSON Structure 15
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Sap S4Hana Sales Order O Data Error Structure
JSON STRUCTURESap S4Hana Sales Order Sales Order Create Structure
JSON STRUCTURESap S4Hana Sales Order Sales Order Item Create Structure
JSON STRUCTURESap S4Hana Sales Order Sales Order Item Structure
JSON STRUCTURESap S4Hana Sales Order Sales Order Item Text Structure
JSON STRUCTURESap S4Hana Sales Order Sales Order Item Update Structure
JSON STRUCTURESap S4Hana Sales Order Sales Order Structure
JSON STRUCTURESap S4Hana Sales Order Sales Order Text Structure
JSON STRUCTURESap S4Hana Sales Order Sales Order Update Structure
JSON STRUCTURESap S4Hana Structure
JSON STRUCTUREScroll within the panel for all 15 ·
Examples 14
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 14 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Order-to-Cash
Automate the sales process from sales order creation through delivery and billing.
Procure-to-Pay
Streamline procurement from purchase requisition through purchase order, receipt, and invoice.
Financial Close
Automate journal entries, cost center reporting, and GL account management for period close.
Supply Chain Visibility
Track inbound and outbound deliveries, inventory movements, and material documents in real time.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
SAP Business Technology Platform
Native integration with SAP BTP for extensions, analytics, and AI/ML capabilities.
SAP Integration Suite
Pre-built integration flows for connecting S/4HANA with third-party applications.
Microsoft Office
Integration with Excel and Outlook for business data analysis and communication workflows.
Resources
Every other property we hold for SAP S/4HANA — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sap-s4hana · machine-readable index on apis.io