> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/api/api-reporter-looker-studio.md).

# Building a Looker Studio dashboard with the Reporter API

Use a Google Apps Script connector, reporter:read, caching, and plan-aware throttling to visualize Rankability tracking data.

## Prerequisites

* A Rankability API key with `reporter:read`.
* Google Looker Studio and Google Apps Script access.

## Use the production base

```
https://rankability.com/api/agent/v1/reporter
```

## Recommended data sources

* `GET /projects` for a project table.
* `GET /projects/:id/trends` for time series.
* `GET /projects/:id/results` for platform detail.
* `GET /summary` for organization-level scorecards.

## Connector pattern

1. Store the API key in connector configuration or a secure property.
2. Fetch the selected Reporter route with a Bearer header.
3. Map stable response fields to Looker Studio dimensions and metrics.
4. Cache API responses in Apps Script.
5. Return rows that match the declared connector schema.

## Rate limits

Limits are 30 requests/min for Solo and Core, 60 for Team, and 120 for Agency. Read the returned rate-limit headers, cache responses, paginate efficiently, and back off after `429`.

## Data freshness

Set Looker Studio freshness to match the client’s tracking cadence. Starting a scan requires `reporter:run` and consumes tracking credits, so do not trigger a scan on every dashboard read.

## Security

Do not expose the API key to dashboard viewers. Use a read-only key dedicated to the connector.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.rankability.com/api/api-reporter-looker-studio.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.