Traini API

Introduction

Learn the conventions, authentication, and request patterns used across the Traini API.

Traini APIs enable developers to process pet voice, behavior, and visual data through a unified intelligence layer. Use these APIs to build applications that understand, interpret, and respond to pet signals in real time.

Using the navigation, you'll find details on endpoints, request formats, and response structures across all Traini APIs.

Authentication

You must include an API key to interact with the Traini API.

API keys are generated in the developer dashboard after your application is approved. All requests should include your API key in the X-Api-Key header.

If you are just getting started, we recommend beginning with the Guides to learn how to create your first integration.

Conventions

The base URL for all API requests is: https://b-api-us.traini.app/api/b/v1.

All requests must be made over HTTPS. The Traini API follows RESTful conventions where possible. Requests are made using standard HTTP methods such as GET and POST, and all request and response bodies are encoded in JSON.

JSON conventions

  • All responses are returned in JSON format
  • Property names use snake_case
  • Numeric values such as confidence scores are returned as decimals
  • Optional fields may return null when not available
  • Timestamps are returned in ISO 8601 format