# Woopra (slim)

> Woopra is a hosted customer journey and product analytics service from Woopra, Inc., an Appier affiliate. Its HTTP tracking API records events and visitor properties, and its REST API returns saved reports, profiles and raw session logs.

- Full: https://www.anchorterminal.com/tools/woopra.md (~7,400 tokens) · this version ~1,930 tokens · JSON https://www.anchorterminal.com/tools/woopra.json · canonical https://www.anchorterminal.com/tools/woopra
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-09

**E · 44.4/100 · rank #779 of 842 · #12 in Product analytics & experimentation · not agent-ready · confidence medium**


Assessment: Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found.

## Facts

- Kind: HTTP API · vendor: Woopra, Inc. · category: Product analytics & experimentation · legal entity: Woopra, Inc. · provenance 77/100
- Endpoint: `https://www.woopra.com/rest/3.10` (HTTP)
- Auth: OAuth or key · pricing: Paid · x402: no · licence: Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC
- Probe metrics: not measured yet (probes haven't run)
- Surface graded: The REST API at https://www.woopra.com/rest/3.10 and the HTTP tracking API at https://www.woopra.com/track. No MCP server was found in the docs
- Report endpoints: GET `/trends`, `/journeys`, `/retention`, `/attribution`, `/activity` and `/profiles`, each taking `project` and the `report_id` of a report saved in the web app
- Profile endpoints: GET `/profile` and `/profile/actions` by `key` and `value` (pid, email, id or cookie), POST `/profile/edit` and `/profile/actions/edit`, DELETE `/profile/delete`
- Raw data: GET `/logs/export` by day in Pacific time with `pos` and the `X-Woopra-NextFile` and `X-Woopra-NextPos` response headers. PUT `/logs/import` takes line-separated JSON and returns a batch ID, and GET `/logs/import` reports its status
- Tracking: GET `/track/ce` and `/track/identify` with `project`, `event`, `cookie` and `cv_`, `ce_` and `cs_` prefixed properties. Responses are 200, 202, 401, 402, 403 or 5XX
- Credentials: REST calls use HTTP Basic with a per-user App ID and Secret Key from the Access Keys tab. Tracking needs no secret unless Secure Tracking is on. No OAuth or scopes found
- Rate limits: 300 calls a minute, 600 an hour and 3,000 a day per project on the REST API, with 429 on excess. No limit on tracking calls was found
- Paging: `limit`, `offset` and a `snapshot` ID on report endpoints, with `timeframe_from` and `timeframe_to` in the project's time zone
- Docs for agents: https://docs.woopra.com/llms.txt and a .md copy of each page, with an OpenAPI 3.1 fragment on each REST reference page. No single spec file found
- SDKs: Browser tracker `@woopra/browser-tracker` (tag v5.3.0 of 15 September 2021, last commit 16 March 2026), iOS 1.2.1 and Android 1.1.0 (last commits November 2024), PHP (2023), Node, Python, Java and Rails (2017), all MIT or ISC
- Plans: Pro from $999 a month for 5 million events, 24 months of retention, 50 seats and a 30-day trial. Enterprise by quote with warehouse sync, SSO and data governance. Overage fees apply past the event quota
- Status: status.woopra.com on Atlassian Statuspage with three components (Data Processing, Data Collection, Front-end Application)
- Sub-processors: Amazon Web Services, Atlassian, Cloudflare, Customer.io, Fastly, GitHub, Google Cloud and Intercom in the USA and Hetzner in Germany, per the terms of service
- Legal: Woopra, Inc., San Francisco, with Appier named as affiliate. EU representative Appier Netherlands B.V. California law, or Singapore law for contracts signed with Appier Pte. Ltd.
- Prices: Pro, 5 million events a month $999 per month (plan)

- Scores: Reliability 80, Performance pending, Schema & documentation 45, Agent ergonomics 45, Security & auth 22, Payments & pricing 30, Task success pending, Maintenance & community 9, Transparency & trust 61 · total over the 7 assessed categories
- Why: Reliability, Graded on the REST and HTTP tracking APIs with the hosted lines. · Schema & documentation, Each REST reference page embeds an OpenAPI 3.1 fragment in its Markdown copy. · Agent ergonomics, Report responses can be capped with `limit`, but a report can only be run from a `report_id` saved in the web app, so an agent can't shape a… · Security & auth, REST calls use per-user access keys sent by HTTP Basic, with no scopes or rotation guidance found. · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, The newest dated change found is a commit to the browser tracker on 16 March 2026, and the REST intro page was last edited on 13 March 2026… · Transparency & trust, Closed service with dated terms that cover the subscription, and MIT SDKs (15).
- Sources: 23, open questions: 9, both in the full twin
- Capabilities: analytics.query, analytics.events, analytics.funnels
- JSON: https://www.anchorterminal.com/api/v1/tools/woopra.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/woopra.svg` or a link to https://www.anchorterminal.com/tools/woopra from a page on woopra.com or one of its subdomains, or the README of github.com/Woopra/js-client-tracker, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Ask the owner to build and save each report in the web app first, then pass the last path segment of its URL as `report_id`
2. Authenticate REST calls with HTTP Basic, using the App ID and Secret Key from the Access Keys tab, against `https://www.woopra.com/rest/3.10/`
3. Stay under 300 calls a minute, 600 an hour and 3,000 a day per project. A 429 carries no documented retry interval, so back off on your own schedule
4. Reuse the `snapshot` ID from the first response when paging with `offset`, or pages past 1,000 records may not agree
5. Send `cookie` or a `cv_` identifier such as `cv_email` on every track call. Without one the event lands on a random profile that can't be identified later
6. When reading `/logs/export`, delete the profile named in each `type: "delete"` line. The following lines log its data again under `new_id`

## Connect

```bash
curl \
--user <App Id>:<Secret Key> \
"https://www.woopra.com/rest/3.10/trends?project=mybusiness.com&start_day=2017-4-12&end_day=2017-5-19&report_id=83mYcoe6jX"
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/woopra

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| PostHog | B | 68.4 | analytics.query, analytics.events, analytics.funnels | https://www.anchorterminal.com/tools/posthog.min.md |
| Amplitude | B | 66.2 | analytics.query, analytics.funnels, analytics.events | https://www.anchorterminal.com/tools/amplitude.min.md |
| Fullstory | B | 62.6 | analytics.query, analytics.events, analytics.funnels | https://www.anchorterminal.com/tools/fullstory.min.md |
| Mixpanel | B | 62 | analytics.query, analytics.funnels, analytics.events | https://www.anchorterminal.com/tools/mixpanel.min.md |
| Countly | C | 54.8 | analytics.query, analytics.events, analytics.funnels | https://www.anchorterminal.com/tools/countly.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)