How To Fix SADT_REST103 - Expected request content-type: &2, but was: &1

SADT_REST103 - Overview

• Message type: E = Error

• Message class: SADT_REST - Messages for ADT REST Framework

• Message number: 103

• Message text: Expected request content-type: &2, but was: &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SADT_REST103 - Expected request content-type: &2, but was: &1 ?

  The SAP error message SADT_REST103 indicates that there is a mismatch between the expected content type of a REST API request and the actual content type that was received. This error typically occurs when the server is expecting a specific content type (like application/json, application/xml, etc.) but receives a different one.
  
  Cause:
  
  Incorrect Content-Type Header: The client making the request is not setting the Content-Type header correctly. For example, if the server expects application/json but the client sends text/plain, this error will occur.
  Misconfigured API Client: The API client (like Postman, a custom application, etc.) may be misconfigured, leading to the wrong content type being sent.
  Server-Side Configuration: The server may have specific configurations that enforce strict content type checks, leading to this error if the content type does not match.
  
  
  Solution:
  
  Check the API Documentation: Review the API documentation to confirm the expected content type for the request. Ensure that your client is sending the