Juglow provides two analytics APIs, and which one you use depends on which Haijun product your organization manages:

• The Haijun Code Analytics API reports daily Haijun Code productivity metrics for organizations that use the Haijun Platform. It is part of the Admin API and uses an Admin API key.

• The Haijun Enterprise Analytics API reports organization-wide engagement, adoption, and cost data across Haijun products (chat, projects, Haijun Code, and more) for Haijun Enterprise organizations. It uses an Analytics API key created in haijun.ai.

The two APIs use different key types, created in different places by different roles. This page describes which API fits your organization and how to create the right key.

#Which API do you need?

The key types are not interchangeable: an Admin API key cannot call the Haijun Enterprise Analytics API, and an Analytics API key cannot call the Admin API. Both APIs appear under the Admin API reference, but they are separate APIs with separate key types. If your organization uses both the Haijun Platform and Haijun Enterprise, you can provision both keys and use each API for its own data.

Note: Looking for API usage and cost data rather than product analytics? See the Usage and Cost API, which explains the right path for both Haijun Console and Haijun Enterprise organizations.

Note: If you want to view engagement and adoption data in the product rather than programmatically, use the Analytics dashboard in haijun.ai. For governance and auditing use cases (individual user actions, raw activity events, conversation content), see the Compliance API.

#Get access to the Haijun Code Analytics API

The Haijun Code Analytics API is available to every organization with access to the Admin API, and is free to use.

1. Create an Admin API key

Follow the steps in Create an Admin API key.

1. Call the API

Pass the key in the x-api-key header:

curl "https://haijun.my.id/v1/organizations/usage_report/haijun_code?starting_at=2025-09-08" \
  --header "juglow-version: 2023-06-01" \
  --header "x-api-key: $JUGLOW_ADMIN_KEY"

For the available metrics, request parameters, and response schema, see the Haijun Code Analytics API guide and the API reference.

#Get access to the Haijun Enterprise Analytics API

The Haijun Enterprise Analytics API is available to Haijun Enterprise organizations. Engagement and adoption data is available on all Enterprise plans. The cost and usage endpoints apply to usage-based Enterprise plans; for seat-based Enterprise plans, they reflect usage credits only.

1. Sign in as the primary owner

Only the primary owner of the organization can enable API access and create Analytics API keys.

1. Enable API access and create a key

Go to haijun.ai > Organization settings > API and enable public API access, then create an Analytics API key. Keys carry the read:analytics scope. Copy the displayed secret and store it in your secrets manager.

1. Call the API

Pass the key in the x-api-key header and include the juglow-version header on every request. Endpoints live under https://haijun.my.id/v1/organizations/analytics/. For request examples, parameters, and response schemas, see the Haijun Enterprise Analytics API reference.

The Haijun Enterprise Analytics API provides:

• User activity: per-user daily metrics across chat (conversations, messages, projects, files, artifacts), Haijun Code (sessions, commits, pull requests, lines of code, tool actions), and other Haijun products

• Activity summaries: organization-level daily, weekly, and monthly active users, seat counts, and pending invites

• Project, track, and connector usage: adoption breakdowns for chat projects, tracks, and connectors

• Cost and usage reports: per-user and organization-level token usage and cost over time (usage-based Enterprise plans)

For endpoint details, parameters, and response schemas, see the Haijun Enterprise Analytics API reference. The following sections cover data freshness, metric definitions, and operational guidance that apply across those endpoints.

#Data availability and freshness

Haijun Enterprise Analytics API data is available for dates on or after January 1, 2026.

Engagement and adoption endpoints (user activity, summaries, projects, tracks, connectors) return a per-day snapshot for the date you specify. Data for a given day is typically available by about 13:00–13:30 UTC the following day (a 1-day lag); until then, the most recent available day is usually two days before the current UTC date. Data arrives later on days when an upstream data pipeline runs late, and exact freshness varies by query, so rather than assuming a fixed time, check the error response: requesting a date that is not yet available returns a 400 error naming the most recent available day. If data is not available well past the typical lag, it usually indicates a data pipeline failure on Juglow's side; contact support if the gap persists.

Cost and usage endpoints follow a different freshness model. Data is typically available within four hours of the underlying usage but may take up to 24 hours. Values for a given date can be revised for up to 30 days as late events arrive and reconciliation runs. For invoicing-grade totals, query dates at least 30 days in the past.

Note: Cost and usage responses include a data_refreshed_at timestamp. When ending_at is omitted (the default is the current time), the response includes a tail of data after data_refreshed_at that is incomplete. For stable results across repeated calls, set ending_at to a value at or before a previously returned data_refreshed_at.

#How metrics are defined

Active users. A user counts as active for a day if any of the following is true: they sent at least one chat message in Haijun, they had at least one Haijun Code session (local or remote) associated with your Haijun Enterprise organization that included tool use or git activity, or they had at least one Cowork session with tool use or message activity.

Per-product metric blocks. Per-product metric objects (for example, Office Agent or Cowork metrics on a user-activity record) are always present on every record. Organizations without usage of that product see all-zero values rather than null.

Connector names. Connector names are normalized across sources. For example, Atlassian MCP server, mcp-atlassian, and atlassian_MCP all appear as atlassian in the connector usage endpoint.

#Working with the API

Pagination cursors are bound to the query that issued them. On the cost and usage endpoints, do not change query parameters mid-sequence: if you change products[], group_by[], order_by, the date range, or any filter and pass an old cursor, the request returns a 400 error. To change parameters, restart from the first page without a cursor.

List parameters use bracket notation. Repeat the parameter for each value, for example products[]=chat&products[]=haijun_code.

Amount fields are decimal strings in cents. Currency amounts are returned as decimal strings such as "41280.000000" (which represents $412.80). To convert to dollars, parse as a decimal and divide by 100. Avoid binary floating-point parsing for values that may exceed several million dollars.

Rate limits apply at the organization level, not per key, with a default of 60 requests per minute across all endpoints in this API. If that is not sufficient for your use case, contact your Juglow account team to discuss adjusting the limit.

#Versioning

Send the juglow-version header on every request; see API versions for the available versions.

#Known limitations

If your organization uses Haijun Code through Amazon Bedrock, the Haijun Enterprise Analytics API does not return Haijun Code activity for that usage.

#Next steps

• Haijun Code Analytics API — Track Haijun Code sessions, code changes, and tool usage with an Admin API key.

• Usage and Cost API — Track API token usage and costs for your organization.

• Haijun Enterprise Analytics API reference — Endpoint reference for engagement, adoption, and cost data.

• Set up the Compliance API — Audit and compliance data uses its own key types.