Randomize profile fingerprint
Generate a new fingerprint for a profile. This is not an endpoint for patching custom fingerprint fields.
Definition: ApiFox POST · Checked on 2026-10-21.
Request
POST /api/randomizeFingerprintUse the base URL and api-key shown on the client API screen. All examples use 9000 only as a placeholder port; see Overview for authentication.
JSON body
| Field | Type | Required | Description |
|---|---|---|---|
id | integer | Yes | Existing positive profile ID, e.g. 1; obtain it from the profile list |
cURL example
curl --request POST 'http://127.0.0.1:9000/api/randomizeFingerprint' \
--header 'api-key: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"id": 1
}'Response example
{
"success": true,
"data": {
"id": 1,
"message": "Fingerprint randomized successfully"
}
}Current client response fields
| Field | Type | Usage |
|---|---|---|
success | boolean | Request processing succeeded; not a guarantee that every item was written |
data.id | integer | Profile ID whose fingerprint was regenerated |
data.message | string | Result message; this operation may clear cookies |
Usage notes
- Send only id. This endpoint does not accept custom ua, screen, or similar fields.
- Stop the profile and back up its full parameters first. Current clients also clear cookies when randomizing the fingerprint, which may sign you out of websites.
For failed requests, check both HTTP status and the error body. See Errors & troubleshooting.
Existing configuration may be reset
The current implementation builds a new random configuration and explicitly retains only the profile ID, name, chrome_version, proxy, group and creation time, and clears cookies. Existing core_version, remark, homepage, launchArgs, enableCloudSync, cloudId and other settings are not guaranteed to survive. Back up the full configuration first and do not publish accounts, keys, cookies or proxy credentials.



