In SAP Cloud Integration, the Content Modifier step modifies message content, headers, or properties. Let’s determine where an APIKey is typically placed:
Step 1: APIKey Usage- An APIKey is a common authentication mechanism for APIs, usually sent as part of the HTTP request to identify the caller.
Step 2: HTTP Standards- Per REST API conventions (and SAP’s implementation), APIKeys are most often included in the HTTP header (e.g., X-API-Key or Authorization), not the body or attachments.
Step 3: Content Modifier Options- In the Content Modifier:
Message Header: Allows adding key-value pairs to the HTTP headers.
Exchange Property: Stores key-value pairs for internal iFlow use, not directly sent in the HTTP request.
Message Body: Contains the payload, not authentication data.
Attachment: For supplementary files, not authentication.
Step 4: Configuration- To send an APIKey in an HTTPS call (e.g., via HTTP adapter), you’d configure the Content Modifier to add it as a header (e.g., Name: X-API-Key, Value: your-api-key).
Step 5: Official Verification- The SAP Help Portal’s "Defining Content Modifier" and "Configuring HTTP Receiver Adapter" sections confirm that headers are used for authentication tokens like APIKeys in outbound calls.
Conclusion: Option A (Message header) is the correct answer.References:
SAP Help Portal: "Defining Content Modifier" (SAP Cloud Integration)
SAP Help Portal: "Configuring HTTP Receiver Adapter"
