In a Lagom Reactive System, the API (servicename-api) part contains the blueprint or interface or contract of that service. It defines the contract or skeleton or template of that API endpoint.
Each API may have one or more endpoints. We define each API endpoint's details in this service, such as the URI of that endpoint, any path parameters, any query parameters, and how to handle a request.
We define a function that actually does the handling of API endpoint requests coming from users, customers, or clients.
We can define this API service as a separate microservice. We will explore how to define API endpoints and how to map them to functions in the coming sections.
