Gameanalytics DataTiger Management API

Name: DataTiger Management API
Brand: DataTiger Management API
Availability: InStock

✓ Official Vendor SpecAnalyticsProduct Analyticsnone70 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the DataTiger Management API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DataTiger Management 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgameanalytics.com%2Fgameanalytics" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgameanalytics.com%2Fgameanalytics" | 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 DataTiger Management API.

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}

GET STARTED

Start building with DataTiger Management API

Explore with Jentic One

View OpenAPI Document

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.

Use Cases

Patterns agents use DataTiger Management API for, with concrete tasks.

★ 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.

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.

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.

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.

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

Key Endpoints

70 endpoints — the datatiger management api is gameanalytics' management surface for the datatiger event pipeline used to ingest, validate, and query game telemetry.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using DataTiger Management API through Jentic.

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.

Gameanalytics DataTiger Management API

Connect the DataTiger Management API to your agent

Capabilities

Start building with DataTiger Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs