canonical: https://jentic.com/apis/gameanalytics.com/gameanalytics

# Gameanalytics DataTiger Management API

The DataTiger Management API is GameAnalytics' management surface for the DataTiger event pipeline used to ingest, validate, and query game telemetry. The 70 operations cover event recording, validation, application user management, type definitions, and proxied integrations with SendGrid and Mandrill template stores. Endpoints are organised under /dev for development-mode telemetry and /data for type and user lookups, with /proxy operations exposing third-party template lists for in-product communications. The API is targeted at game studios, publishers, and live-ops teams that already use GameAnalytics for player telemetry and need a programmatic surface to manage event schemas, validate payloads, and orchestrate engagement messaging.

## For AI agents

Manage GameAnalytics DataTiger event ingestion, validation, application users, and proxied template lookups across 70 management endpoints under api.datatiger.com.

## Scope

Does not handle player payment processing, ad-network attribution, or live multiplayer state - use for DataTiger event recording, validation, user lookup, and template proxying only.

## Capabilities

- Record game events for development applications via `/dev/events`
- Validate event payloads before production ingestion through `/dev/events/validate`
- Look up application user records with `/dev/applications/{application}/users/{userId}`
- Browse event type definitions via `/data/types` and user metadata via `/data/user`
- Pull SendGrid template lists through the `/proxy/sendgridTemplates` passthrough endpoint
- Pull Mandrill template lists through the `/proxy/mandrillTemplates` passthrough endpoint

## Use cases

### Pre-Production Event Validation

Validate every new game telemetry event payload against DataTiger's type definitions during development by calling `/dev/events/validate`, catching schema regressions before they reach the live ingestion pipeline. Studios can wire the validator into client-side build tooling and pull-request checks.

Example prompt: Call POST `/dev/events/validate` with the candidate event payload and surface any validation errors in the build output.

### Live-Ops Player Lookup

Look up a specific player by application and user id via `/dev/applications/{application}/users/{userId}` so live-ops support can confirm event history and account state when investigating a ticket. The endpoint returns the structured user record from DataTiger.

Example prompt: Call GET `/dev/applications/{application}/users/{userId}` with the IDs from the support ticket and return the user record.

### Engagement Template Catalogue

Power an in-game messaging composer that lists available SendGrid and Mandrill templates by calling `/proxy/sendgridTemplates` and `/proxy/mandrillTemplates`, so designers can pick a template without leaving the game backoffice. The proxy endpoints centralise authentication for both providers.

Example prompt: Call GET `/proxy/sendgridTemplates` and GET `/proxy/mandrillTemplates` and merge the responses into a single picker list.

### Agent-Driven Telemetry QA via Jentic

A QA agent receives a request like 'check that this new tutorial-complete event is valid' and uses Jentic to discover `/dev/events/validate`, load its schema, and execute the call against the studio's DataTiger workspace. Jentic isolates the workspace credential so the agent never holds it directly.

Example prompt: Search Jentic for 'validate datatiger event', load `/dev/events/validate`, and execute it with the proposed event payload.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/dev/events` | Record a development-mode event |
| POST | `/dev/events/validate` | Validate an event payload against its type |
| GET | `/dev/applications/{application}/users/{userId}` | Look up an application user |
| GET | `/data/types` | List event type definitions |
| GET | `/data/user` | Retrieve user metadata |
| GET | `/proxy/sendgridTemplates` | List SendGrid templates |
| GET | `/proxy/mandrillTemplates` | List Mandrill templates |

## Key resources

- **Events** — Record and validate development-mode game events via `/dev/events` and `/dev/events/validate.`
- **Applications** — Inspect application user records via `/dev/applications/{application}/users/{userId}.`
- **Types** — Browse event type definitions via `/data/types.`
- **Users** — Look up user metadata via `/data/user.`
- **Proxy** — Pull SendGrid and Mandrill template lists via /proxy/* endpoints.

## Why Jentic

- **Setup:** Wiring the DataTiger Management API by hand means pointing at api.datatiger.com and coordinating event recording, validation, user lookup, and template-proxy calls yourself. Through Jentic you install once, import the DataTiger Management API from the API Directory, and your agent calls it.
- **Permission scoping:** DataTiger puts the application and user ids in the URL path (`/dev/applications/{application}/users/{userId}`), so a rule can pin your agent to one application: it can look up users within that application and nothing else. You choose the operations it may call, so event recording or template proxying is not included unless you add it.
- **Credential handling:** Any DataTiger credential you supply is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'record a DataTiger event' or 'look up a user in an application', and Jentic returns the matching DataTiger operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel API** — General product-analytics API used as an alternative to GameAnalytics outside game-specific workflows.
- **Amplitude HTTP API** — Behavioural-analytics API with strong cohort and retention features overlapping DataTiger's event surface.

## FAQ

### What authentication does the DataTiger Management API use?

The OpenAPI spec does not declare a securityScheme, which means callers should follow GameAnalytics' partner-issued credential model published with their workspace. When called through Jentic, any required credential is held encrypted in the vault and injected at execution.

### Can I validate a game event payload before sending it to production?

Yes. POST `/dev/events/validate` accepts a candidate event payload and returns whether it conforms to the registered type, so studios can gate production ingestion on a successful validation in CI.

### What are the rate limits for the DataTiger Management API?

The OpenAPI spec for `/dev/events`, `/data/types`, and the /proxy template endpoints does not declare numeric rate limits. Watch for HTTP 429 responses and consult GameAnalytics partner support for any account-specific throughput agreements.

### How do I list SendGrid templates through Jentic?

Run a Jentic search for 'list sendgrid templates from datatiger', load GET `/proxy/sendgridTemplates`, and execute it. Get started with Jentic One, the self-hosted execution layer.

### Can I look up a specific application user by id?

Yes. GET `/dev/applications/{application}/users/{userId}` returns the structured user record so live-ops and QA can investigate state for an individual player without joining raw event tables.

### Can I limit what my agent is allowed to do with the DataTiger Management API?

Yes. Because you run Jentic One yourself, your own rules decide which DataTiger operations and credentials your agent can use. Since DataTiger carries the application and user ids in the URL path, such as `/dev/applications/{application}/users/{userId}`, you can pin the agent to a single application so it only looks up users within that application and nothing else. You also pick the exact operations it may call, so event recording via `/dev/events` or template proxying via `/proxy/sendgridTemplates` stays off unless you explicitly add it.