In the context of SAP API Management, a target endpoint is the backend service that an API proxy invokes after processing a request from a client. The target endpoint represents the actual service provider. This can be the original backend service, defined by its URL, which is exposed by an API provider (A). The core configuration of a target endpoint is the URL of the original API (E) that the proxy will call. Additionally, in a scenario known as proxy chaining, one API proxy (D) can act as a local target endpoint for another, allowing for the composition of services.

B. API consumer: An API consumer is the client application that initiates the call to the API proxy, not the backend service that the proxy calls.

C. Resources: Resources are the specific paths (e.g., /orders, /products) within an API's URL, not the backend service endpoint itself.

1. SAP Help Portal

SAP Integration Suite

Understanding API Proxies: "An API proxy is an intermediary for a backend service that you want to expose... The API proxy then redirects the request to the backend service. The backend service is also referred to as a target endpoint." This supports that the target endpoint is the backend service provided by the API provider (A).

2. SAP Help Portal

SAP Integration Suite

Target Endpoint: "A TargetEndpoint configuration configures the URL for the backend service and defines how an API proxy connects to that backend service." This directly confirms that the URL of the original API (E) is a key component of the target endpoint.

3. SAP Help Portal

SAP Integration Suite

Chaining API Proxies: "API proxy chaining is invoking one API proxy from another. You can implement proxy chaining when you have an API proxy that needs to call another API proxy... To chain proxies

you use a local target connection to make a request from one proxy to another..." This confirms that an API proxy (D) can be a target endpoint.