Screening
List screenings
The team's screenings, newest first, optionally for one company (companyId) or person (personId), with hit counts and how many hits still wait for a decision. Paged with the AG Grid request model (startRow, endRow).
Lists the team’s screenings, newest first, optionally for one company or person, with how many hits are new and how many still wait for a decision. Requires the pep scope on the API key.
Paged with the AG Grid request model. See Reviewing hits for the row properties and who sees which screenings.
Authorization
x-api-keystringheaderrequiredYour API key, sent in the x-api-key header.
Query parameters
companyIdintegerOnly screenings of this company
personIdintegerOnly screenings of this person
Bodyapplication/json
startRowintegerendRowintegerrowGroupColsRowGroupModel[] | nullHide child attributes
idstring | nulldisplayNamestring | nullfieldstring | nullgroupKeysstring[] | nullfilterModelFilterModel[] | nullHide child attributes
columnNamestring | nullcolumnNameWithAliasstring | nullread-onlyfilterTypestring | nullsortModelSortModel[] | nullHide child attributes
sortstringcolIdstring | nullResponses
AG Grid page of TeamScreeningListItem_Dto rows
Try it with a grid
A server-side data grid bound to this endpoint through the proxy. Sort and filter columns and watch the request body the grid sends; the response arrives as rows with lastrow.
Stored in this browser only (until you forget it) and sent as the x-api-key header through the documentation proxy.
Enter your API key to load the grid.
{ "startRow": 0, "endRow": 50, "sortModel": [], "filterModel": {} } Sort or filter a column and the request body updates; the response arrives as rows and lastrow.