Tasklist has public endpoints in C8 REST API

[engineering-issue-sync-app[bot]]

Value Proposition Statement

Use intuitive and consistent experience via a single, unified Camunda 8 API to query task data

User Problem

Customers perceive complexity when working with Camunda 8, handling multiple available API technologies - REST, gRPC, as well as the deprecated GraphQL API. There is no single C8 API. Users have to mix and match various APIs (Tasklist, Operate, Zeebe) to implement their use case.

As our APIs are fragmented, each component follows a different standard to build API i.e. request and response formats are different. Authentication, authorization and tenancy is implemented differently as well.

It's unclear for new users, which API to use and they have to explore the schema of different components' endpoints by themselves.

Release Notes

You can now use the unified Camunda 8 REST API to solve different automation use cases that previously required to use of different components' APIs. Easily find task data in a single API.

User Stories

• As a developer, I can use C8 API to query data that were previously in Tasklist API
• As a Developer, I'm sure all endpoints use the same schema for request and response
• As a Developer, I can find all endpoints available for use and documentation in an OpenAPI schema and text-based documentation at docs.camunda.io. I can find information about all endpoints, which consist of the:
  • A clear description of what the endpoint is about
  • Name, type, and description of each parameter, including whether it’s optional or required
  • All possible responses, including expected\/possible error codes and their descriptions
  • Any deprecated endpoints should be identified
  • Models or schemas
• As a Developer, I can use officially supported SDKs and API tools to explore and interact with migrated endpoints. Specifically, I can use the:
  • Camunda Java and Spring SDK
  • Postman
  • Other supported SDKs (i.e. NodeJS SDK)

Implementation Notes

### Entities to migrate
- [ ] Form
- [ ] Task
- [ ] Variables

• Implementation should follow the example's structure, built in https://github.com/camunda/product-hub/issues/2274
• Endpoints structure: POST .../v2/resource/search
• All near-real-time (query from ES/OS) needs to be POST endpoints. Only real-time (Zeebe) endpoints are GET
• Endpoints should be built in a way that Tasklist FE application can use them instead of internal API / Tasklist API v1
• As part of this epic, we should check if any data other data needs to be added in existing endpoints
• As part of this epic, we won't build new endpoints, that were not present in Tasklist REST API V1

^{:robot: This issue is automatically synced from: source}