GET /api/repos/:repoId/overrides

Summary

Retrieves all file overrides for a specified repository.

Intent

Allows clients to fetch the list of file overrides associated with a given repository, optionally scoped to a specific customer for access control purposes.

Parameters

Name	Type	Required	Description
repoId	string	Yes	The unique identifier of the repository whose overrides should be retrieved.
customerId	string	No	Optional customer identifier. If provided, the request will be rejected with 403 if the repository does not belong to this customer.

Request example

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

Response example

{
  "overrides": [
    {
      "filePath": "src/routes/users.ts",
      "action": "include"
    },
    {
      "filePath": "src/routes/internal.ts",
      "action": "exclude"
    }
  ]
}

Error cases

• 404 — No repository exists with the given repoId
• 403 — A customerId query parameter was provided but does not match the customerId associated with the repository

Gotchas

• The customerId query parameter is optional, but if supplied it acts as an ownership check — a mismatch returns 403 even if the repo exists.
• Omitting customerId entirely bypasses the ownership check, so any caller with a valid repoId can retrieve overrides without customer scoping.
• The response field is named ‘overrides’ (plural) — do not expect a singular ‘override’ key.
• Auth is not strictly enforced at the framework level (auth required: false), meaning the Authorization header may not be validated server-side, but should still be sent as a best practice.