Fingerprints

Fingerprints are currently exposed in the original flat payload format.

Format

The payload stores one protocol view in a single object, with fields such as http_version, tls_ciphers, http2_settings, headers, and header_order.

HTTP/3-capable fingerprints add http3_settings, http3_headers, http3_header_order, and quic_transport_parameters. These fields, along with WebSocket-specific fields, are available through the public API to pro users.

Related reference

See the curl-cffi fingerprint documentation for background on the fingerprint format: https://curl-cffi.readthedocs.io/en/latest/fingerprints.html

CI maintenance API

CI automation can update or delete a fingerprint with PUT /api/v1/fingerprints/:id and DELETE /api/v1/fingerprints/:id. Send the configured CI key through X-API-Key or a bearer authorization header. User API keys, including pro keys, cannot use these operations.