Reading REST Endpoint Docs
5 exercises on reading REST endpoint references — decode methods, path and query parameters, status codes and rate-limit headers.
Key patterns
{id}in a path = a required path parameter- Anything after
?joined by&= query parameters 201created,204no content,400bad input,401auth,403permission,404missing,429rate-limitedX-RateLimit-Remaining= calls left;Reset= a Unix timestamp
0 / 5 completed
1 / 5
Read this REST endpoint reference:
GET /v1/projects/{projectId}/issues/{issueId}
Path parameters
projectId string required The project the issue belongs to.
issueId string required The issue to retrieve.
Responses
200 OK The issue object is returned.
404 Not Found No issue with that id exists in the project.What does {issueId} in the path represent?Curly braces in a path = a path parameter.
In API docs, a token wrapped in
In API docs, a token wrapped in
{...} inside the URL is a path parameter (also called a path variable or URL segment). You replace it with a real value, e.g. GET /v1/projects/web-app/issues/482.- Path parameter — lives inside the path:
/issues/{issueId}. Usually identifies one specific resource. - Query parameter — comes after
?:?status=open. Usually filters or paginates a collection. - Header — metadata such as
Authorization, never shown in the path.
required, so omitting either gives you a malformed URL, not a valid request. Common phrasing: "supply the resource identifier as a path parameter".