Skip to main content
POST
/
data-lists
Create data list
curl --request POST \
  --url http://api.gu1.ai/data-lists \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "<string>",
  "type": "<string>",
  "description": "<string>",
  "source": "<string>",
  "config": {},
  "fieldMappings": {},
  "priority": 123,
  "isGlobal": true
}
'

​
Overview

Creates a new data list for the organization. Use type: "custom" for a generic list you will reference by UUID in rules.

​
Endpoint

POST https://api.gu1.ai/data-lists

​
Authentication

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

​
Request Body

​
name
string
required
Display name (1–200 characters). Shown in the dashboard (list catalog, selectors, headers) so your team can identify the list; it does not affect how rules match items.
​
type
string
required
List type enum, including custom, company_blocklist, document_blocklist, keyword_list, ip_blocklist, and others supported by the platform.
​
description
string
Optional description (max 1000 characters). Use for internal context (owner, refresh policy, intended use case); visible in the dashboard where the product shows list details. Not used by the matching engine.
​
source
string
required
Origin of data, e.g. manual_entry, api_integration, custom_upload, internal, etc.
​
config
object
Optional: autoSync, syncFrequency, externalUrl, apiKey, visibleItemDataColumns, etc.
​
fieldMappings
object
Optional string-to-string map for ingestion mappings.
​
priority
number
default:"50"
Priority 1–100.
​
isGlobal
boolean
Reserved for platform use; tenant clients normally omit or set false.

​
Example

{
  "name": "High-risk merchants",
  "description": "Internal blocklist for KYB rules",
  "type": "custom",
  "source": "api_integration"
}

​
Response

201 with success, data (includes list id), and timing metadata on success.