canonical: https://jentic.com/apis/observepoint.com/observepoint

# ObservePoint Grid Reports API

The ObservePoint Grid Reports API returns ObservePoint's web governance and tag audit data in row and column format. You request grid data for an entity type with filters, read the schema that describes each grid's columns, and save, list, update, and delete report definitions so a query can be reused. Favouriting marks the reports a team relies on, and an export operation kicks off a downloadable extract of a grid. Analytics and QA teams use it to pull tag and page audit results into their own dashboards and pipelines.

## For AI agents

Query ObservePoint grid audit data by entity type, read a grid's column schema, manage saved report definitions, and start data exports. Authenticates with an API key sent in the Authorization header.

## Scope

Does not configure audits, crawl websites, or manage users. Use for querying grid audit data, managing saved report definitions, and starting exports only.

## Capabilities

- Query grid audit data for an entity type with filters
- Read the schema that describes a grid's columns
- Create, list, read, update, and delete saved report definitions
- Mark a saved report as a favourite or remove that mark
- Start an export of a grid's data for download

## Use cases

### Feed audit data into a dashboard

An analytics agent queries ObservePoint grid data for an entity type, reads the grid schema so it knows each column, and writes the rows into a reporting dashboard. This surfaces tag and page audit results next to other metrics without a person exporting spreadsheets. Through Jentic the agent discovers the grid-data operation by intent and calls it with the entity type and filters.

Example prompt: Query the grid data for a given entity type and return the rows along with the grid's column schema

### Reuse saved report definitions

Instead of rebuilding a query each time, an agent creates a saved report definition, lists the saved reports, and runs the one it needs on a schedule. It can update a saved report's filters as requirements change and delete definitions that are no longer used. This keeps a team's standard audits consistent across runs.

Example prompt: Create a saved report definition, then list the saved reports and confirm the new one appears

### Export a grid for offline analysis

When a team needs the full result set outside the platform, an agent starts an export of a grid and hands off the extract for offline analysis or archival. This moves large audit results into a data warehouse or spreadsheet without paging the API row by row. The export runs as its own operation the agent can trigger on demand.

Example prompt: Start an export of the grid for a given entity type and return the export request confirmation

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v3/reports/grid/{gridEntityType}` | Query grid audit data for an entity type |
| GET | `/v3/reports/grid/{gridEntityType}/schema` | Read the column schema for a grid |
| POST | `/v3/reports/grid/saved` | Create a saved report definition |
| GET | `/v3/reports/grid/saved` | List saved report definitions |
| GET | `/v3/reports/grid/saved/{id}` | Read a single saved report definition |
| POST | `/v3/reports/grid/{gridEntityType}/exports` | Start an export of a grid's data |

## Key resources

- **Grid data** — Query audit data for an entity type and read its column schema
- **Saved reports** — Create, list, read, update, and delete saved report definitions
- **Exports** — Start a downloadable export of a grid

## Why Jentic

- **Setup:** Wiring the ObservePoint Grid Reports API by hand means setting the API key in the Authorization header, building the grid-data request bodies and filters, and handling saved reports and export jobs yourself. Through Jentic you install once, import the ObservePoint Grid Reports API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The ObservePoint Grid Reports API addresses each saved report by an id in the URL path, so you can scope the agent to the reports and operations it needs: allow it to query grid data and read saved reports and leave report deletion out of the allowed set unless you add it.
- **Credential handling:** Your ObservePoint API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get grid report data' or 'export a report', and Jentic returns the matching ObservePoint operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Mixpanel API** — Product analytics event data versus ObservePoint's tag and page audit grids.
- **Amplitude API** — Another product-analytics platform focused on behavioural events rather than tag governance.
- **Segment API** — Segment routes the analytics events that ObservePoint audits for correct implementation.

## FAQ

### What authentication does the ObservePoint Grid Reports API use?

The ObservePoint Grid Reports API authenticates with an API key that you send in the Authorization header of each request. Through Jentic the key is stored encrypted by your own Jentic One instance and supplied to requests at execution time, so the agent never sees the raw value.

### How do I query grid data with the ObservePoint Grid Reports API?

Request grid data for an entity type with your filters in the request body, and read the grid schema first so you know each column the response returns. An agent can then write the rows into a dashboard or pipeline alongside its other metrics.

### Can I reuse report definitions in the ObservePoint Grid Reports API?

Yes. You can create a saved report definition, list the saved reports, read one by its id, and update or delete it. Favouriting marks the reports a team relies on, so an agent can run a standard audit consistently across scheduled runs.

### What are the rate limits for the ObservePoint Grid Reports API?

The OpenAPI spec does not declare rate limits for the ObservePoint Grid Reports API. Apply conservative client-side throttling, back off on HTTP 429 responses, and check ObservePoint's developer documentation for the current published limits.

### Can I limit what my agent is allowed to do with the ObservePoint Grid Reports API?

Yes. You choose which operations the agent may call, so it can be allowed to query grid data and read saved reports while report deletion stays out of the allowed set unless you add it. Because each saved report is addressed by an id in the URL path, you can keep the agent to the reports it needs, and every call it makes is logged.

### Is there an ObservePoint API MCP server?

You don't need an MCP server to give your agent the ObservePoint Grid Reports API. Jentic connects it directly from the API Directory: import it, store the key once, and your agent calls the grid-data, saved-report, and export operations on demand without a separate server to run.

### How do I pull ObservePoint grid data through Jentic?

Search Jentic for an intent like 'get grid report data' or 'export a report', which returns the matching ObservePoint operation with its input schema so the agent supplies the entity type and filters and reads the response. To run it on your own infrastructure, install Jentic One from its GitHub repo.