Intuizi

Read the caller's POI data (GET /api/v2/my-data/pois/...). kind selects the collection: segments, categories, brands, pois, submissions. Pass id for a single record (pois and submissions only). Extra arguments become query parameters (search, page, per_page where supported).

browse_poi_data

Request cooperative cancellation of an in-flight Lookalike Model run (POST /api/v2/analyses/audiences/cancel-lookalike). The worker stops at its next progress checkpoint; a finished run returns an error.

cancel_lookalike

Create a POI brand (POST /api/v2/my-data/pois/brands/create). Body fields exactly as documented at https://console.intuizi.com/developers/api/v2/poi.

create_poi_brand

Create a POI category (POST /api/v2/my-data/pois/categories/create). Body fields exactly as documented at https://console.intuizi.com/developers/api/v2/poi.

create_poi_category

Submit POIs as an inline list (POST /api/v2/my-data/pois/submissions/create-by-list). Body fields exactly as documented at https://console.intuizi.com/developers/api/v2/poi. For file-based submissions, reserve an upload with create_upload (purpose poi_submission), have the file PUT to the presigned URL, then call the raw API endpoint create-by-upload with the upload_reference.

create_poi_submission

Activate a Completed audience to a partner endpoint connection (POST /api/v2/analyses/activations/create). Body fields exactly as documented at https://console.intuizi.com/developers/api/v2/activations. Discover endpoint_connection_id via lookup_reference endpoint-connections, then pricing-models and datastreams (both need that connection's partner_id). The audience must be Completed first (get_audience data[0].status.id = 104). FREQUENCY FILTER: freq_min / freq_max only apply when freq_limit is true, and are REJECTED (422) when sent without an explicit freq_limit - never applied implicitly. To activate a previewed range, send the same freq_min / freq_max as preview_activation with freq_limit=true and its filter_hash; the server recomputes the hash and rejects any mismatch (different range, or an audience rebuilt since the preview). The response echoes filters and filter_hash.

create_activation

Reserve an upload slot (POST /api/v2/uploads/create) and receive a presigned single-key PUT URL plus a one-shot upload_reference. IMPORTANT: this tool cannot transfer file bytes itself - hand the returned upload_url to the user (or to a tool that can make an HTTP PUT) so the file is uploaded before its expiry, then pass upload_reference to create_cohort (purpose cohort) or to the POI create-by-upload endpoint (purpose poi_submission). Full contract at https://console.intuizi.com/developers/api/v2/uploads.

create_upload

Create an audience (POST /api/v2/analyses/audiences/create). The datasets array holds one or two dataset blocks EXACTLY as documented at https://console.intuizi.com/developers/api/v2/audiences - discover valid filter values via lookup_reference first. A key a dataset type does not define (a misspelling, another type's key, or a filter the type lacks - Deidentified has NO device/OS filter, its fields object only selects output columns) is rejected with 422 naming the key; fix the payload rather than retrying. Poll get_audience until data[0].status.id is 104 (Completed). Writable dataset types: POI, WebDomain, CTV, Apps, Cohorts, AffinityTransactions, Demographics, Deidentified, ProfileAttributes, Origin. A POI block (store visitation) REQUIRES start_date, end_date, signal_providers and location.countries, plus at least one of categories, analysisdata or locations. The BRAND field is called analysisdata - a flat list of POI brand ids from lookup_reference(dataset="poi", catalog="brands"). There is no "brands" key on this type and brands are NEVER nested inside categories: categories is a flat list of integer POI category ids from lookup_reference(dataset="poi", catalog="categories"), and an object there is rejected with 422. Geography goes on the block as location.countries / location.states / location.cities / location.zipcodes (the poi/locations catalog also takes states and cities to narrow the list it returns). So "Ford dealerships in California last week" is {"type":"POI","analysisdata":[<Ford brand id>],"location":{"countries":["USA"],"states":["CA"]},...}. The type the console labels "Transactions" is AffinityTransactions - purchase-affinity data, United States only. Its block REQUIRES start_date, end_date and signal_providers (the common fields every type except Cohorts and Demographics carries) plus at least one of categories (affinity category ids) or brands (affinity brand id strings). Optional: subcategories (MCC description strings), incomes, ages, genders, ethnicities, channels ("B&M" and/or "ONLINE"), spend_min, spend_max, txn_min, txn_max, analysis_spend_frequency, analysis_transactions_frequency, max_devices_per_ip (1-5, default 3), and location.states / location.cities / location.zipcodes (location.countries is optional and always stored as ["USA"]; location.dmas is rejected). end_date cannot run past the most recent fully-settled purchase week. Resolve categories, subcategories, brands, incomes, ages, genders and ethnicities with lookup_reference(dataset="affinity-transactions", ...); signal_providers with lookup_reference(dataset="common", catalog="signal-providers", dataType="AffinityTransactions"); and the geo arrays from the common states / cities / zipcodes catalogs. The earlier "Transactions" dataset (merchants / spend / frequency bands) is retired and rejected here. A WebDomain block's start_date must fall within the last 45 days of available web data - older visitation data is archived and rejected. A ProfileAttributes block REQUIRES start_date, end_date, signal_providers and profile_attributes: a list of {category_id, key, value_ids} rows AND-ed together. Note the field is value_ids (integer ids), NOT values (raw strings) - resolve them with lookup_reference(dataset="profile-attributes", catalog="values", key="<key>"), whose items carry the id in "value" and the underlying data in "raw_value"; resolve category_id and key with the sibling "categories" and "keys" catalogs. Dates are QUARTER-ALIGNED and must fall inside the delivered window returned by lookup_reference(dataset="profile-attributes", catalog="recency-limits"). location is NOT supported for this type - the dataset carries no geography and the builder discards it, so location.countries is optional (accepted for backward compatibility, never applied) and states / cities / zipcodes / dmas are rejected. An Origin block targets devices by their resolved HOME location (where they originate), not by places visited. Its only filters are geographic: it REQUIRES start_date, end_date, signal_providers (from lookup_reference(dataset="common", catalog="signal-providers", dataType="Origin")) and location.countries, and optionally narrows by location.states, location.cities, location.dmas (the DMA label strings from lookup_reference(dataset="common", catalog="dmas"), never numeric codes) and location.zipcodes. It defines no other filter key. Its data is WEEKLY with no day in it: any dates are accepted, but the window is widened to the whole Monday-to-Sunday weeks it touches (Tuesday to Friday builds, and is stored as, that full week), so a sub-week window cannot be built - tell the user the widened window. Coverage is limited to a few countries - discover them with lookup_reference(dataset="common", catalog="countries", datasetType="Origin"). The build counts toward the company's monthly data-scan limit and is refused with a 422 once that limit is reached (check get_usage).

create_audience

Create a cohort (POST /api/v2/analyses/cohorts/create). Body fields exactly as documented at https://console.intuizi.com/developers/api/v2/cohorts. Two sources: with source "file" (the default) supply exactly ONE of file_uri (a cloud file the caller owns) or upload_reference (from create_upload with purpose cohort, after the file was PUT to the presigned URL) plus identifier_type/identifier_column - use preview_cohort_file first to confirm identifier_column. With source "audience" supply audience_id (a Completed audience the caller owns; a regular audience makes at most one cohort, a Lookalike Model can make several) and a limit: freq_limit with freq_min/freq_max (and optional is_day_part), or distance_limit with distance (meters), or - Lookalike Model audiences only - score_limit with min_score/max_score (0 to 1, band upper bounds of the model score histogram, min at most max; the cohort keeps the best-scored EIDs first, capped by device_limit), or neither for a device limit (optional device_limit). The audience cohort takes its name from the audience.

create_cohort

Build a Lookalike Model from a completed seed audience (POST /api/v2/analyses/audiences/create-lookalike). Seed rules: pick a seed from list_audiences whose data[0].status.id is 104, whose is_lookalike is false, and whose results_count is at least 1,000 devices (by default). target_size max 4,000,000 by default. The result is a NEW audience (is_lookalike true) - poll it with get_audience until data[0].status.id is 104. Requires the Lookalike capability on the account; a 403 means it is not enabled.

create_lookalike_audience