AD Base Entities3

AD Users11

AIA CAs3

Alerts17

Analysis3

API Info2

API Tokens3

Asset Isolation33

Asset Scores1

Attack Paths11

Audit1

Auth14

Azure Entities1

BloodHound Users12

Cert Templates3

Client Ingest1

Clients24

Collection Uploads6

Collectors6

Computers16

Config4

Containers2

Custom Node Management5

Cypher12

Data Quality6

Database1

Datapipe4

Domains17

Enterprise CAs4

EULA1

Events (Schedules)5

GPOs6

Graph7

Groups10

Jobs9

Meta Entities1

NT Auth Stores3

OpenGraph (Experimental)8

OUs5

Permissions2

Risk Posture2

Roles2

Root CAs3

Search2

Tasks9

Collection Uploads

Community

Enterprise

List File Upload Jobs

Lists available file upload jobs

get/api/v2/file-upload

Query parameters

sort_bystring

Sort by column. Can be used multiple times; prepend a hyphen for descending order. See parameter description for details about which columns are sortable.

Sortable columns are user_email_address, status, status_message, start_time, end_time, last_ingest, id, created_at, updated_at, and deleted_at.

user_idstring

Filter results by column string value. Valid filter predicates are eq, ~eq, neq.

user_email_addressstring

Filter results by column string value. Valid filter predicates are eq, ~eq, neq.

statusstring

Filter results by column integer value. Valid filter predicates are eq, neq, gt, gte, lt, lte.

status_messagestring

Filter results by column string value. Valid filter predicates are eq, ~eq, neq.

start_timestring

Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.

end_timestring

Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.

last_ingeststring

Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.

idstring

Filter results by column integer value. Valid filter predicates are eq, neq, gt, gte, lt, lte.

created_atstring

Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.

Filter results by created_at value. See filter schema details for valid predicates.

updated_atstring

Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.

Filter results by updated_at value. See filter schema details for valid predicates.

deleted_atstring

Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.

Filter results by deleted_at value. See filter schema details for valid predicates.

skipinteger

The number of items to skip in a paginated response.

This query parameter is used for determining the number of objects to skip in pagination.

limitinteger

The limit of results requested by the client.

This query parameter is used for setting an upper limit of objects returned in paginated responses.

Response

OK

countinteger

The total number of results.

skipinteger

The number of items to skip in a paginated response.

limitinteger

The limit of results requested by the client.

Changes

Changed in 4 of the 66 revisions of this API.3838

Apr 1, 202640bf219eced6118See the full diff
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ to the query request parameter id
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ to the query request parameter status
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter created_at
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter deleted_at
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter end_time
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter last_ingest
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter start_time
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter updated_at
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter status_message
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter user_email_address
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter user_id
  request-parameter-pattern-added
- ○
  for the query request parameter created_at, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter deleted_at, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter end_time, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter id, the type/format was generalized from integer/ to string/
  request-parameter-type-generalized
- ○
  for the query request parameter last_ingest, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter start_time, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter status, the type/format was generalized from integer/ to string/
  request-parameter-type-generalized
- ○
  for the query request parameter updated_at, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
Apr 1, 20266aaeba6ecdc5811See the full diff
- ▲
  for the query request parameter created_at, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter deleted_at, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter end_time, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter id, the type/format was changed from string/ to integer/
  request-parameter-type-changed
- ▲
  for the query request parameter last_ingest, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter start_time, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter status, the type/format was changed from string/ to integer/
  request-parameter-type-changed
- ▲
  for the query request parameter updated_at, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ from the query request parameter id
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ from the query request parameter status
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter created_at
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter deleted_at
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter end_time
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter last_ingest
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter start_time
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter updated_at
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter status_message
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter user_email_address
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter user_id
  request-parameter-pattern-removed
Apr 1, 2026674e0a229e8a118See the full diff
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ to the query request parameter id
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ to the query request parameter status
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter created_at
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter deleted_at
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter end_time
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter last_ingest
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter start_time
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ to the query request parameter updated_at
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter status_message
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter user_email_address
  request-parameter-pattern-added
- ▲
  added the pattern ^((eq|~eq|neq):)?[^:]+$ to the query request parameter user_id
  request-parameter-pattern-added
- ○
  for the query request parameter created_at, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter deleted_at, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter end_time, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter id, the type/format was generalized from integer/ to string/
  request-parameter-type-generalized
- ○
  for the query request parameter last_ingest, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter start_time, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
- ○
  for the query request parameter status, the type/format was generalized from integer/ to string/
  request-parameter-type-generalized
- ○
  for the query request parameter updated_at, the type/format was generalized from string/date-time to string/
  request-parameter-type-generalized
Jan 12, 2026a426ff0abf8f811See the full diff
- ▲
  for the query request parameter created_at, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter deleted_at, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter end_time, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter id, the type/format was changed from string/ to integer/
  request-parameter-type-changed
- ▲
  for the query request parameter last_ingest, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter start_time, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ▲
  for the query request parameter status, the type/format was changed from string/ to integer/
  request-parameter-type-changed
- ▲
  for the query request parameter updated_at, the type/format was changed from string/ to string/date-time
  request-parameter-type-changed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ from the query request parameter id
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$ from the query request parameter status
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter created_at
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter deleted_at
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter end_time
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter last_ingest
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter start_time
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$ from the query request parameter updated_at
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter status_message
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter user_email_address
  request-parameter-pattern-removed
- ○
  removed the pattern ^((eq|~eq|neq):)?[^:]+$ from the query request parameter user_id
  request-parameter-pattern-removed
This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog