# Reporting Solutions

Operational and financial visibility across your portfolio. Pick the option based on how much automation you need and who will consume the data.

### Pick a Reporting Option

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Reporting API</strong></td><td>Most automation. Pull report data into your systems.</td><td><a href="/spaces/j9heLdoDRsfnChUQohvj/pages/gc3X2wHXftsasfDb19Ai">Learn more</a></td></tr><tr><td><strong>Partner Portal (view and export)</strong></td><td>No build. View reports in the portal and export to CSV or Excel.</td><td><a href="/spaces/ek5aF2vccbKrklw8djdB/pages/cfdafc08272ac56a5ba730402d0302912eecf613">Learn more</a></td></tr></tbody></table>

{% hint style="info" %}
Rule of thumb:

* Need automated ingestion (BI, data warehouse, scheduled pulls): use the **Reporting API**.
* Need ad-hoc reporting with downloads: use **Partner Portal**.
  {% endhint %}

### Comparison Matrix

| Criteria               | [Reporting API](/api-reference/api/reporting.md)                 | [Partner Portal](/getting-started/getting-started/our-products/partner-and-merchant-solutions/partner-portal.md) |
| ---------------------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Primary goal**       | Programmatic access to report data.                              | View reports and export files.                                                                                   |
| **Best for**           | Engineering + data teams building automated reporting pipelines. | Ops, finance, and support teams needing self-serve access.                                                       |
| **Integration effort** | Medium to high (API integration).                                | None (portal access).                                                                                            |
| **Automation**         | High (schedule jobs, sync into internal tools).                  | Low (manual view/export).                                                                                        |
| **Output**             | API responses for direct processing.                             | CSV and Excel exports.                                                                                           |
| **Access control**     | API keys and integration controls.                               | Role-based access in the portal.                                                                                 |

### Next Step

* Using the **Reporting API**: start with the [Reporting API Reference](/api-reference/api/reporting.md).
* Using **Partner Portal**: open the reports area and export what you need.

### Need Help?

{% hint style="success" %}
Tell us what reports you need and how often you need them.

We’ll recommend the cleanest Reporting API vs. Partner Portal setup for your workflow.

<a href="https://xplorpay.com/getting-started/" class="button primary">Get in touch</a>
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.xplorpay.com/getting-started/getting-started/our-products/reporting-solutions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.