Define the GET operation for the /employees/{id} path

Use z/OS® Connect Designer to define the z/OS Assets for your API.

This topic is applicable to: z/OS Connect Designer capability Content applicable to application developers

Paths are endpoints or resources that are exposed by your API, such as /employees. Each resource has one or more operations, which are HTTP methods that are used to manipulate these resources. For example, GET, PUT, POST, or DELETE.

The paths are defined by the OpenAPI definition that you imported in the task Starting the z/OS Connect Designer with Docker and importing an OpenAPI definition. In the z/OS Connect Designer, the available operations appear in the left navigation under Paths.

Figure 1. The paths page
The paths page

You create z/OS Assets to configure the relationship between your API request and the endpoint. For example, you create a z/OS Asset called getEmployee that uses the GET/employees/{id}/ path to retrieve information about a specific employee from Db2®.