GreenHill ReportQuest API

Authenticated access to GreenHill account, performance, and reporting data.

Open interactive API documentation Agent guide llms.txt

For people

Open the interactive documentation above. The page will prompt for your ReportQuest personal access token (PAT) before it loads the protected OpenAPI definition. The PAT is kept only in the current browser tab and is sent to this API as Authorization: Bearer <PAT>.

Do not put a PAT in a URL, bookmark, screenshot, or support message. PATs remain valid until they expire or are revoked.

For agents and integrations

Start with the public /llms.txt, then read the public /agent-guide.md. They explain credential recognition, identity verification, account resolution, contract discovery, and reporting safeguards for a zero-context agent.

The OpenAPI document, Reporting Recipes, and API operations are protected. They accept the same Bearer header with either an API-issued JWT or a PAT:

Authorization: Bearer <JWT_OR_PAT>

GET /swagger/v1/swagger.json — current OpenAPI contract
GET /api/v1/Reporting/Recipes — agentic reporting recipes
GET /api/v1/Users/WhoAmI — authenticated identity check

Optional JWT exchange

A client can use its PAT directly or exchange it for a time-limited API JWT:

POST /api/v1/Auth/Token
Authorization: Token <PAT>

The exchange does not invalidate the PAT. Use the returned access_token on subsequent requests as Authorization: Bearer <access_token>.