> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/data-quality/understanding-object-counts.md).

# Understanding Object Counts

Every number on the Data Quality page is a live count of OCPI objects ENAPI currently holds for that module and party.

### These are raw counts

This is the single most important thing to understand about the page — especially if you're landing here from a commercial context and expect the numbers to match your dashboard.

**Counts include everything ENAPI has received, in every state.** Specifically:

* **Locations** with `publish=false`, and locations in every status — including `REMOVED`.
* **Tokens** that are expired, revoked, or otherwise no longer valid.
* **Tariffs** that aren't currently linked to any connector.

That means the Data Quality count will almost always be higher than the "active" equivalent in your own system. If your platform shows 1,200 active locations and ENAPI shows 1,450, that's not necessarily a problem — the delta is likely inactive, unpublished, or removed objects that ENAPI is still storing.

When you verify against your own system, compare against your **full object set in all states**, not just active.

### Your Data

Shows data organized by your platforms and parties. Use it to check: is ENAPI holding the same set of objects my platform is pushing? If the count is materially lower than your full object set (active + inactive + removed), ENAPI may be missing data — typically a sync issue on specific objects.

### Partner Data

Shows data ENAPI has received from your partners and is making available to you. Use it to check what you have from each partner. The most useful comparison here isn't against some expected number — it's against your own system: does your platform reflect the same set of partner objects ENAPI is showing?

### Gaps and discrepancies

Where an expected count is known — for example when a partner reports a total in their OCPI response headers — ENAPI compares it against what actually came through. A gap means some objects didn't sync. These are flagged on the page and investigable via the [The Sync Activity Log](https://docs.enapi.com/data-quality/the-sync-activity-log.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.enapi.com/data-quality/understanding-object-counts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
