Localytics Query API

Name: Localytics Query API
Brand: Localytics Query API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsProduct Analyticsbasic5 EndpointsREST

For Agents

List Localytics apps, inspect the attributes available for each app, and run custom analytical queries to retrieve product usage data.

Install Jentic One Beta

Connect the Localytics Query API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Localytics Query 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.

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 | sh

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 instance

Jentic 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 Localytics Query API.

List the apps configured in a Localytics account

Retrieve the attribute schema available for a specific app

Run custom analytical queries against an app's event and attribute data

GET STARTED

Start building with Localytics Query API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Localytics Query API, keeping it validated and agent-ready. Localytics is a mobile and web product analytics platform, and this Query API exposes the analytical data store to external tools. Endpoints cover listing apps, listing the attributes available on each app, and running custom queries against the data set. It is meant to be called from BI tools, scheduled reports, and agent workflows that need to read product usage data programmatically. Authentication is HTTP Basic.

Use Cases

Patterns agents use Localytics Query API for, with concrete tasks.

★ Scheduled Product Analytics Export

Product teams running on Localytics often need a daily export of key metrics into a data warehouse or BI tool. The /v1/query endpoint accepts custom queries and returns aggregated results. Combined with /v1/apps to enumerate apps and /v1/apps/{app_id}/attributes to enumerate filters, a scheduled job can keep the warehouse in sync without manual exports.

Loop GET /v1/apps to enumerate apps, then call GET /v1/query for each app with the metric query and load results into the warehouse table.

Marketing Campaign Reporting

Marketing teams want to track event counts and conversions per campaign. Using /v1/apps/{app_id}/attributes to discover which attributes are available, an integration constructs a query against /v1/query to pull conversions broken down by campaign. The resulting numbers feed into the marketing team's reporting dashboards.

Call GET /v1/apps/{app_id}/attributes to confirm the campaign attribute exists, then GET /v1/query with the conversion event grouped by that attribute.

AI Agent Product Analytics Q&A

An AI agent answering product manager questions like 'how many users opened the app yesterday?' can use Jentic to run Localytics queries directly. The agent searches Jentic for the query operation, executes it with the right metric and date filter, and returns the answer in plain language. The Localytics API credential stays in the Jentic vault.

Use Jentic to call GET /v1/query with the daily active users metric for the relevant app and yesterday's date and return the count to the user.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for localytics query api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/apps

List apps in the account

GET

/v1/apps/{app_id}

Retrieve a specific app

GET

/v1/apps/{app_id}/attributes

List attributes available on the app

GET

/v1/query

Run a custom analytical query

GET

/v1/apps

List apps in the account

GET

/v1/apps/{app_id}

Retrieve a specific app

GET

/v1/apps/{app_id}/attributes

List attributes available on the app

GET

/v1/query

Run a custom analytical query

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Localytics Basic Auth credentials are stored encrypted in the Jentic vault. The Authorization header is injected at execution time, so raw username and password values never enter agent context, logs, or LLM traces.

Intent-based discovery

Agents search Jentic for intents like 'run a product analytics query' and Jentic returns the matching Localytics operations with their input schemas, so an agent can answer analytics questions without browsing the Localytics docs.

Time to first call

Direct Localytics Query API integration: 1 day for Basic Auth setup, app discovery, attribute introspection, and query construction. Through Jentic: under an hour to search, load, and execute.

FAQs

Specific to using Localytics Query API through Jentic.

Why is there no official OpenAPI spec for Localytics Query API?

Localytics does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Localytics Query API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Localytics Query API use?

The Query API uses HTTP Basic authentication with a Localytics API username and password. Through Jentic, the credentials are stored encrypted in the vault and injected as the Authorization header at execution time, so the raw values never enter agent context.

Can I run a custom analytical query directly via the API?

Yes. The /v1/query endpoint accepts a query specifying the app, metric, dimensions, and date range, and returns aggregated results. Use /v1/apps/{app_id}/attributes first to confirm which attributes are available for grouping or filtering.

What are the rate limits for the Localytics Query API?

Rate limits are not declared in the spec. Localytics applies account-level rate limits and dataset-size guidance for the Query API; large historical pulls should be batched by date range to avoid timeouts.

How do I run a Localytics query through Jentic?

Search Jentic for 'run a Localytics analytics query'. Jentic returns the GET /v1/query operation. Load the schema, supply the app ID, metric, and filters, and execute. The response is the aggregated result ready for downstream reporting.

Which apps can I query?

You can query any app present in the authenticated account. Call GET /v1/apps to enumerate them, then pass the app_id of interest to /v1/apps/{app_id}/attributes and /v1/query.