GET /api/repos

Summary

Retrieves a list of repositories associated with a specific customer.

Intent

Allows clients to fetch all repositories belonging to a given customer, enabling downstream processing such as documentation generation or pipeline runs scoped to that customer.

Parameters

Name	Type	Required	Description
customerId	string	Yes	The unique identifier of the customer whose repositories should be listed.

Request example

curl -X GET "https://maps.google.com/api/repos?customerId=cust-456" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json"

Response example

{
  "repos": [
    {
      "id": "repo-123",
      "name": "acme/api",
      "customerId": "cust-456"
    },
    {
      "id": "repo-456",
      "name": "acme/frontend",
      "customerId": "cust-456"
    }
  ]
}

Error cases

• 401 — customerId query parameter is missing from the request

Gotchas

• Despite the handler returning a 401 status code for a missing customerId, this is semantically a missing required parameter error (400-like), not an authentication failure — the status code choice is unconventional.
• customerId must be passed as a query parameter (e.g., ?customerId=cust-456), not in the request body or as a path segment.
• The endpoint is declared with auth required: false in the route configuration, but the handler still enforces the presence of customerId and returns 401 if absent — ensure your client always supplies this parameter.
• The response shape is { repos: […] } — the array is nested under the ‘repos’ key, not returned as a top-level array.