nextCursor from the response to a follow-up request that uses the same conditions.
1. Base URL
GET/Face-auth
2. Authentication
Include the FaceAuth project API key in thex-api-key header.
x-api-key
This is a separate API key from your Liveform API key. See Add-on Overview — Checking the add-on API key.
3. Request Example
GET/Face-auth
startDate and endDate must be sent together.
Date range
4. Request Parameters
integer
The maximum number of records to return. The default is
100, the minimum is 10, and the maximum is 200.string
The
nextCursor value from the previous list response. Pass the server-issued value verbatim. It carries a signature, so modifying any part of it returns 400 REQUEST_INVALID. It cannot be assembled by hand or reused with different lookup conditions.string
The start of the lookup range, in
yyyy-MM-dd'T'HH:mm:ss.SSSZ RFC 3339 UTC format. Must be sent together with endDate.string
The end of the lookup range, in RFC 3339 UTC format. It cannot be earlier than
startDate. Both bounds are inclusive.5. Response
result.json
5-1. Success
A successful list lookup returns200 OK with the body below.
array
The array of results. Each element is a FaceAuthSubmission object. It is an empty array when nothing matches.
nullable · string
The value to pass as the
cursor parameter of the next page request. null when there is no next page.It is a signed token in the form v1.{payload}.{signature}. The payload holds the position of the last item and the lookup conditions and is base64-encoded, so it can be decoded — but the signature is bound to the lookup conditions, so changing the value or reusing it with different conditions fails validation. Do not depend on its structure; pass back exactly what you received. The format may change without notice.- The response body has exactly two top-level fields:
itemsandnextCursor. - The list can include deleted submissions. A completed deletion has a value in
deleteTime.
5-2. Failure
A failed list lookup returns an HTTP status code with an error object.6. Error Responses
Errors returned by the ARGOS application use the{ code, message } format. 401 and some 403 responses are blocked at the authentication layer and do not follow that format — see FaceAuth Common Reference — Authentication layer errors.