Options for FingerprintJS server API client
Readonly
apiReadonly
authenticationReadonly
regionDelete data by visitor ID Request deleting all data associated with the specified visitor ID. This API is useful for compliance with privacy regulations. All delete requests are queued: Recent data (10 days or newer) belonging to the specified visitor will be deleted within 24 hours. * Data from older (11 days or more) identification events will be deleted after 90 days. If you are interested in using this API, please contact our support team to activate it for you. Otherwise, you will receive a 403.
The visitor ID you want to delete.*
Promise that resolves when the deletion request is successfully queued
client
.deleteVisitorData('<visitorId>')
.then(() => {
// Data deletion request was successfully queued
})
.catch((error) => {
if (isDeleteVisitorError(error)) {
console.log(error.statusCode, error.message)
}
})
Retrieves a specific identification event with the information from each activated product — Identification and all active Smart signals.
identifier of the event
client
.getEvent('<requestId>')
.then((result) => console.log(result))
.catch((err) => {
if (isEventError(err)) {
// You can also access the raw response
console.log(err.response)
console.log(`error ${err.statusCode}: `, err.message)
} else {
console.log('unknown error: ', err)
}
})
Retrieves event history for the specific visitor using the given filter, returns a promise with visitor history response.
Identifier of the visitor
Optional
filter: { Visitor history filter
Optional
before?: number⚠️ Deprecated pagination method, please use paginationKey
instead. Timestamp (in milliseconds since epoch) used to paginate results.
Optional
limit?: numberLimit scanned results.
For performance reasons, the API first scans some number of events before filtering them. Use limit
to specify how many events are scanned before they are filtered by requestId
or linkedId
. Results are always returned sorted by the timestamp (most recent first).
By default, the most recent 100 visits are scanned, the maximum is 500.
Optional
linked_Filter visits by your custom identifier.
You can use linkedId
to associate identification requests with your own identifier, for example: session ID, purchase ID, or transaction ID. You can then use this linked_id
parameter to retrieve all events associated with your custom identifier.
Optional
paginationUse paginationKey
to get the next page of results.
When more results are available (e.g., you requested 200 results using limit
parameter, but a total of 600 results are available), the paginationKey
top-level attribute is added to the response. The key corresponds to the requestId
of the last returned event. In the following request, use that value in the paginationKey
parameter to get the next page of results:
GET api-base-url/visitors/:visitorId?limit=200
response.paginationKey
to get the next page of results: GET api-base-url/visitors/:visitorId?limit=200&paginationKey=1683900801733.Ogvu1j
Pagination happens during scanning and before filtering, so you can get less visits than the limit
you specified with more available on the next page. When there are no more results available for scanning, the paginationKey
attribute is not returned.
Optional
request_Filter visits by requestId
.
Every identification request has a unique identifier associated with it called requestId
. This identifier is returned to the client in the identification result. When you filter visits by requestId
, only one visit will be returned.
client
.getVisitorHistory('<visitorId>', { limit: 1 })
.then((visitorHistory) => {
console.log(visitorHistory)
})
.catch((error) => {
if (isVisitorsError(error)) {
console.log(error.statusCode, error.message)
if (error.status === 429) {
retryLater(error.retryAfter) // Needs to be implemented on your side
}
}
})
Update an event with a given request ID
Data to update the event with.
Optional
linkedLinkedID value to assign to the existing event
Optional
suspect?: booleanSuspect flag indicating observed suspicious or fraudulent event
Optional
tag?: Record<string, never>Full tag
value to be set to the existing event. Replaces any existing tag
payload completely.
The unique event identifier.
Change information in existing events specified by requestId
or flag suspicious events.
When an event is created, it is assigned linkedId
and tag
submitted through the JS agent parameters. This information might not be available on the client so the Server API allows for updating the attributes after the fact.
Warning It's not possible to update events older than 10 days.
const body = {
linkedId: 'linked_id',
suspect: false,
}
client
.updateEvent(body, '<requestId>')
.then(() => {
// Event was successfully updated
})
.catch((error) => {
if (isUpdateEventError(error)) {
console.log(error.statusCode, error.message)
}
})
FingerprintJS server API client used to fetch data from FingerprintJS