Fetch intelligent search result

get/intelligent/search/result

Query parameters

idstring required

Search id (e.g. "61202067-543e-4e6a-8c23-11f9b8f008cf")

limitinteger

Result limit

mediainteger required

Define the type of media to search for.
0: Not set. (All media types)
1: Paste document
2: Paste User
3: Forum
4: Forum Board
5: Forum Thread
6: Forum Post
7: Forum User
8: Screenshot of a Website
9: HTML copy of a website.
10: Invalid, do not use.
11: Invalid, do not use.
12: Invalid, do not use.
13: Tweet
14: URL, high-level item having HTML copies as linked sub-items
15: PDF document
16: Word document
17: Excel document
18: Powerpoint document
19: Picture
20: Audio file
21: Video file
22: Container files including ZIP, RAR, TAR and others
23: HTML file
24: Text file

statisticsinteger

Add statistics

previewlinesinteger

Preview lines count

bucketstring

Specify the bucket to search
See list of buckets https://blog.intelx.io/2022/05/05/list-of-buckets/

dateFromstring

Example:2024-01-01 00:00:00

Date from of the result in YYYY-mm-dd HH:ii:ss format. (Not RFC3339)

dateTostring

Example:2024-01-31 23:59:59

Date to of the result in YYYY-mm-dd HH:ii:ss format. (Not RFC3339)

reset0 | 1

Reset previous searches

Response

Intelligent search result page. The client is expected to poll this endpoint repeatedly and interpret the status code:

0 = Success with results (continue polling, more results available) 1 = No more results available (this response might still have results) 2 = Search ID not found 3 = No results yet available, keep trying 4 = Error

status0 | 1 | 2 | 3 | 4 required

Status of the search result: 0 = Success with results (continue polling) 1 = No more results available 2 = Search ID not found 3 = No results yet available, keep trying 4 = Error

Example response

{
  "records": [
    {
      "added": "2024-01-31 23:59:59",
      "date": "2024-01-31 23:59:59"
    }
  ]
}

Changes

Changed in 4 of the 12 revisions of this API.310

Dec 4, 2025c421471d8fe324See the full diff
- ▲
  the records/items/allOf[Item]/added response's property type/format changed from string/date-time to string/ for status 200
  response-property-type-changed
- ▲
  the records/items/allOf[Item]/date response's property type/format changed from string/date-time to string/ for status 200
  response-property-type-changed
- ○
  for the query request parameter dateFrom, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter dateTo, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  the records/items/allOf[Item]/added response's property pattern ^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}$ was added for the status 200
  response-property-pattern-added
- ○
  the records/items/allOf[Item]/date response's property pattern ^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}$ was added for the status 200
  response-property-pattern-added
Nov 20, 2025a27ca98b01bd5See the full diff
- ○
  added the non-success response with the status 400
  response-non-success-status-added
- ○
  added the non-success response with the status 401
  response-non-success-status-added
- ○
  added the non-success response with the status 404
  response-non-success-status-added
- ○
  added the non-success response with the status 500
  response-non-success-status-added
- ○
  added the success response with the status 200
  response-success-status-added
Nov 19, 2025722b0ddb9ec41See the full diff
- ○
  endpoint added
  endpoint-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Nov 14, 2025218f8a8b89521See the full diff
- ▲
  api path removed without deprecation
  api-path-removed-without-deprecation
This revision also has 6 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history