ERP
Pull daily visitors alongside sales so conversion is a field in the system your finance team already lives in.
Every figure in the dashboard is available over a plain REST call. One key per tenant, JSON out, no SDK to install.
Each tenant has its own API key. Send it as a bearer token or as
x-api-key — they are interchangeable. The key is the tenant: every row you
read belongs to whoever owns the key, and nothing in the URL can point at another tenant's data.
Authorization: Bearer <your_api_key> — or — x-api-key: <your_api_key>
One row per store per day, or the full hour-by-hour breakdown. Both take the same filters.
| Parameter | Meaning |
|---|---|
from / to | Inclusive date range, YYYY-MM-DD |
siteId | One store. Omit for all of them |
limit | Maximum rows, up to 50 000 |
One row per store per day. visitors is total in,
exits is total out.
curl -H "Authorization: Bearer <your_api_key>" \ "https://app.pcountr.com/api/daily?from=2026-09-01&to=2026-09-15" [ { "date": "2026-09-01", "siteId": "118", "visitors": 303, "exits": 329, "peakHour": 17 } ]
One row per store per day per hour. ins and
outs are the counts for that hour, in store-local time.
curl -H "Authorization: Bearer <your_api_key>" \ "https://app.pcountr.com/api/hourly?from=2026-09-01&to=2026-09-15" [ { "date": "2026-09-01", "hour": 17, "siteId": "118", "ins": 41, "outs": 38 } ]
Pull daily visitors alongside sales so conversion is a field in the system your finance team already lives in.
Power BI, Tableau, Looker or a plain scheduled script — it is JSON over HTTPS, so anything can read it.
Attach real store traffic to campaigns and promotions, and measure what a push actually brought through the door.
siteId, so you can start without them.YYYY-MM-DD. Ranges are inclusive at both ends.Hours with no traffic are absent rather than zero, and there is no server-side period total — sum the days yourself. Responses cap at 50 000 rows, so split a long period into windows.
Tell us what you are integrating with and we will point you at the right endpoint.