Skip to content
Getting Started
Overview
.md

Overview

The Intuizi API is the REST API behind the Intuizi console. With it you query Intuizi’s Large Behavioral Model, our flagship large quantitative model (LQM), trained on de-identified, real-world behavioral signals: build audiences from it, size them, and deliver them to your partners.

Base URL 

https://console.intuizi.com

All endpoints live under the /api/v2/ path prefix. For example:

https://console.intuizi.com/api/v2/auth/login
https://console.intuizi.com/api/v2/my-data/pois/segments/index

What the API covers today

  • Authentication - exchange console credentials for a bearer token.
  • My POI Data - manage your company’s POI data: segments, categories and brands, your POI locations with full detail, and POI submissions (create by file, upload or list, read, delete).
  • Audiences - create an audience against one or two datasets (with AND / OR / NOTIN operators and optional crossvisitation and cross purchase), then list, get and delete them. Estimate an audience’s size before creating it.
  • Lookalike Models - grow a completed seed audience into a larger set of similar devices.
  • Cohorts - build cohorts from a file in your own cloud, an upload, or a completed audience.
  • Activations - activate a completed audience to an endpoint connection, then list, get and delete activations. Preview how many devices a frequency range would deliver before activating it.
  • Schedules - rebuild a completed audience on a recurring data window, optionally re-exporting it each cycle.
  • Projects - group audiences, activations and cohorts under a project.
  • Webhooks - list your registered webhook endpoints (read-only; management is in the console) and their event schema.
  • Usage - your company’s current-month data-scan usage and monthly limit.
  • Reference data - the read-only catalogs that power the audience builder: shared Common catalogs (geography, languages, signal providers, activation destinations, data stream visualizations) and per-dataset Dataset Types catalogs.

Every list read accepts an optional search query parameter (case-insensitive contains on the item name).

See Concepts for the shared conventions that apply across every endpoint.

Content types

Every request must send and accept JSON:

Content-Type: application/json
Accept: application/json

A request without Accept: application/json is rejected with 406 Not Acceptable.

Authentication