Key API Management components in SAP Integration Suite:

API Designer → Used to design APIs, import specifications (OpenAPI, RAML), and define metadata.

Product → Groups one or more APIs into a package that can be published to API Business Hub Enterprise.

Other options:

Authorization Server → Part of security infrastructure, not a direct API Management component.

API Entity → Not a defined component; the actual entities are API Proxies, Providers, and Products.

Thus, correct components are API Designer and Product.

In SAP Cloud Integration, dynamic configuration values (headers, properties, body elements) are accessed using Expression Language (EL) notation:

${header.} → Accesses a message header value.

${property.} → Accesses a message property.

${body} → Accesses the payload.

Therefore, when you want to set an Entry ID in a Data Store Write operation using a header value, the correct syntax is ${header.receiver}.

When using API Key authentication for HTTP(S) calls in SAP Integration Suite:

The API Key is typically included in the HTTP header (e.g., APIKey: or x-api-key: ).

Message headers are configured in the Content Modifier for outbound requests.

Other options:

Attachment → Used for file handling, not authentication.

Message body → Contains payload, not credentials.

Exchange property → Used internally within the flow, not sent externally.

Thus, the API Key must be placed in the Message header.