API Management for SAP Landscapes

Keep this: job aid

API Management checklist for SAP landscapes

• Agree the OpenAPI contract, including error responses, before building.
• Prefer SAP released APIs from the SAP Business Accelerator Hub over custom services.
• One API provider per backend connection; proxies named by business capability.
• Version in the base path; never break a published version.
• Proxy request PreFlow: key or token check first, then Spike Arrest, Quota, threat protection.
• Target side: strip consumer keys, add backend credentials from encrypted storage.
• Shape errors into the agreed body; strip internal headers and host names.
• Products by consumer need; internal and external apart; approval for partners.
• Test backend, proxy and every policy's negative path; keep a versioned request collection.
• Watch analytics weekly in hypercare: usage, latency split, error codes, quota use.