Inconsistent id field usage in job creation and retrieval

When creating a job with POST /api/v1/jobs, the response returns the job identifier as "id".
However, when querying the job status with GET /api/v1/jobs/{ID}, the API docs/examples suggest using "ID" (uppercase), which introduces confusion

In my workflow (using n8n), this causes issues because:

Create Job response → id (lowercase)

Check Job endpoint → requires ID (uppercase)

To make the API consistent and easier to integrate, it would be better if the field naming was uniform (id in both request/response and path params). Is that make sense?