Heap API
✓ Official Vendor SpecAnalyticsProduct AnalyticsapiKey, basic6 EndpointsREST
For Agents
Track server-side events, identify users, attach user and account properties, and run bulk operations or privacy-driven user deletions in Heap.
Use for: I need to track a server-side event in Heap for a backend purchase, Identify a Heap user once they log in, Attach a plan tier property to a Heap user, Add an account-level property such as MRR for a Heap account
Not supported: Does not handle session replay, A/B testing, or report querying — use for server-side event ingestion and user/account property enrichment only.
Heap is a digital analytics platform that automatically captures user interactions in web and mobile apps. The server-side API supplements the autocapture by letting backend services track custom events, identify users, attach user and account properties, and submit bulk operations. It also exposes a privacy endpoint for user deletion and an integration-track variant for partner platforms. Product, growth, and data teams use it to enrich autocaptured client events with server-known facts like billing tier, signup source, or backend-only events.
Install Jentic One Beta
Connect the Heap API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Heap API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Heap API.
Track custom server-side events through POST /api/track
Identify a user and attach a user_id through POST /api/v1/identify
Add or update user-level properties via POST /api/add_user_properties
Add or update account-level properties via POST /api/add_account_properties
Send partner-integration events through POST /api/integrations/track
Mint a public auth token via POST /api/public/v0/auth_token for downstream calls
Use Cases
Patterns agents use Heap API for, with concrete tasks.
★ Server-Side Conversion Tracking
Some conversions — payment captures, subscription upgrades, refunds — happen on the backend and are not visible to the autocapture script. POST /api/track to record these events with the user identity and any context properties so they appear in Heap funnels alongside client events. This gives a complete picture of the user journey end-to-end.
POST /api/track with identity, event 'subscription_upgraded', and properties { plan: 'pro' } and verify HTTP 200
User and Account Property Enrichment
Heap's autocapture cannot see facts like billing plan, customer success tier, or industry segment. Use /api/add_user_properties and /api/add_account_properties to push those values from the backend so analysts can segment the entire autocaptured event stream by them. Bulk-update properties on schedule whenever the source-of-truth in your CRM or billing system changes.
POST /api/add_user_properties for a user with properties { plan: 'enterprise', mrr: 1500 } and confirm a 200 response
Privacy-Compliant User Identification
After a user signs up or logs in, POST /api/v1/identify to bind the anonymous Heap session to your stable user_id, then push a known-user event through /api/track. This stitches anonymous and identified sessions in Heap reports and supports privacy operations because every event is tied to an identifiable user_id you control.
POST /api/v1/identify with the user's email and your internal user_id immediately after login
AI Agent Analytics Updates via Jentic
An ops agent watching billing webhooks searches Jentic for 'update analytics user properties' and Jentic returns Heap's /api/add_user_properties operation. The agent reads the new MRR from the webhook payload and pushes it to Heap, all without holding the Heap app_id directly because Jentic vaults it. This makes Heap a write-target for agent-driven enrichment workflows.
Use Jentic search 'update analytics user properties' to load /api/add_user_properties and execute with the user's email and MRR
Key Endpoints
6 endpoints — heap is a digital analytics platform that automatically captures user interactions in web and mobile apps.
METHOD
PATH
DESCRIPTION
POST
/api/track
Track a server-side event
POST
/api/v1/identify
Identify a user
POST
/api/add_user_properties
Add user-level properties
POST
/api/add_account_properties
Add account-level properties
POST
/api/integrations/track
Send a partner-integration event
POST
/api/public/v0/auth_token
Mint a public auth token
POST
/api/track
Track a server-side event
POST
/api/v1/identify
Identify a user
POST
/api/add_user_properties
Add user-level properties
POST
/api/add_account_properties
Add account-level properties
POST
/api/integrations/track
Send a partner-integration event
POST
/api/public/v0/auth_token
Mint a public auth token
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Heap's app_id grants ingestion rights for the project. Jentic stores it in the vault (MAXsystem) and injects the app_id header at execution time, so agents only see scoped tool results.
Intent-based discovery
Agents search Jentic for 'track an event' or 'update analytics user properties' and Jentic returns Heap's /api/track, /api/v1/identify, or property endpoints with their input schemas.
Time to first call
Direct Heap integration: half a day to wire identify, track, and property flows. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Heap API through Jentic.
What authentication does the Heap API use?
The API supports two schemes: an app_id header (apiKey scheme) for the standard server-side endpoints, and HTTP Basic auth on /api/public/v0/auth_token. Jentic stores the app_id in the vault and attaches it on each call.
Can I track events server-side with the Heap API?
Yes. POST /api/track with your app_id, the user identity, an event name, and any custom properties. The event then appears alongside autocaptured client events in your Heap project.
How do I attach a custom property to a user?
POST /api/add_user_properties with the user's identity (identity or email) and a properties object. The properties are merged onto the user's profile and become available for segmentation in Heap reports.
What are the rate limits for the Heap API?
Heap does not publish a single hard rate limit, but high-volume integrations should batch via the integrations-track and bulk endpoints rather than per-event posts. The EU region is hosted at c.eu.heap-api.com — point your client there to keep traffic in-region.
How do I update a Heap user property through Jentic?
Search Jentic for 'update analytics user properties', load the /api/add_user_properties operation for heap.io, and execute with the user's email and the property to set. Jentic injects the app_id from the vault.
Does Heap support EU data residency?
Yes. The spec lists https://c.eu.heap-api.com as an alternative server. Use it as the base URL for projects provisioned in the EU region; the endpoint paths are identical to the US server.
GET STARTED