Endpoint · Search

Save an event search

Save a list of filter conditions and get back a `queryId` to pass to GET /v1/events.

POST/v1/search/events

Authentication

Bearer token in the Authorization header. The token reaches what your plan covers. Getting a token.

Parameters

Request body

queryarray·bodyrequired
Chips, in order. A condition chip is { fieldType, label, value, operator }. A join chip is { fieldType: "Operator", label, value } with AND or OR, placed between conditions. See search and filtering.

Response

success holds the object below.

  • queryIduuidPass to GET /v1/events?queryId=….
  • ignored_field_typesarrayField types that were accepted but will not filter anything. Treat a non-empty list as an error.

Saving the same chips twice returns the same queryId, so it's safe to call before every search. Saved searches don't expire.

An invalid chip returns 400 with Invalid chip data detected.

Examples

Set CHIKARA_API_TOKEN and each sample runs as written. Example records are invented.

curl -sS -X POST "https://api.chikaraintel.com/v1/search/events" \
  -H "Authorization: Bearer $CHIKARA_API_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "query": [
      {
        "fieldType": "EventType",
        "label": "move",
        "value": "move",
        "operator": "EQUAL"
      },
      {
        "fieldType": "Operator",
        "label": "AND",
        "value": "AND"
      },
      {
        "fieldType": "MoveType",
        "label": "Departure",
        "value": "Departure",
        "operator": "EQUAL"
      }
    ]
  }'

See pagination and errors.

Used by

MCP tools built on this endpoint.

Related