Intermediate Reading #api-docs #rest #http-status

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
  • 201 created, 204 no content, 400 bad input, 401 auth, 403 permission, 404 missing, 429 rate-limited
  • X-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?