Why API-based tools can't reach these sources
A reporting dashboard that works through APIs is only as broad as the APIs available to it. If a platform doesn't publish one, or publishes one too limited to return the figures you need, there's no connector to build. Carrier portals, older insurance and finance systems, and many internal dashboards fall into this category: the data is real and visible, but it's locked behind a login with no programmatic door.
The usual fallback is to do it by hand — log in, export or copy the numbers, paste them into a spreadsheet, then into a report template. That reaches the data, but it's slow, error-prone, and has to be repeated every reporting cycle. Neither the API tools nor the manual route is a good fit when the source you care about has no API.
How reportr reads the portal you're already in
reportr is a Chrome extension that works inside your own authenticated session. When you open a portal tab you're logged into, it reads the data from that page: it uses the official API where the source has a good one, and reads the already-rendered page where there isn't one. Extraction is client-side — it doesn't log in for you, doesn't bypass access controls, and doesn't centrally warehouse the data. Host permissions are narrow and consent is granted per source.
Because the extraction is tied to a specific portal's layout, reportr carries a capture health signal that flags whether each run came back clean, empty or layout-drifted, or unmatched. If a portal changes its page structure, that signal warns you rather than letting a blank report ship. The output is the same branded PDF you'd get from any source — the only difference is that this one had no API to begin with.
Three ways to report from a no-API source
| API-based tools | Export and paste by hand | reportr | |
|---|---|---|---|
| Reaches sources with no API | No | Yes | Yes |
| How it gets the data | Platform API connector | You export/copy manually | Reads the portal you're logged into (API or rendered page) |
| Repeated each cycle | Automatic, where supported | Manual every time | One click each time |
| Risk of transcription errors | Low | High | Low |
| Warns on layout/empty capture | N/A | No | Yes, capture health signal |
| Where data is processed | Vendor servers | Your machine | Client-side, your session |
frequently asked
- Why can't AgencyAnalytics or Whatagraph pull from a carrier portal?
- Those tools connect through platform APIs. A carrier portal that publishes no usable API has nothing for them to connect to, so the data stays out of reach. reportr reads the portal page directly in your session instead.
- Does reportr log in to the portal or scrape it from a server?
- Neither. It works inside the session you're already logged into, in your own browser. Extraction is client-side, it doesn't log in for you, and it doesn't centrally warehouse the data. Permissions are narrow and granted per source.
- What happens if the portal changes its layout?
- reportr's capture health signal distinguishes a clean capture from an empty or layout-drifted one and from unmatched results, so a broken adapter warns you instead of producing a blank report.
- Does it use APIs at all?
- Yes, where they're good. The approach is hybrid: it uses the official API when a source has a usable one and reads the already-rendered page only where there isn't. The point is that it isn't limited to sources that publish an API.
Last updated June 8, 2026