Rotate Bot traffic token
PUT https://datafa.st/api/v1/admin/websites/{websiteId}/bot-traffic/tokenReplace the website's
dfbot_ token. The previous token stops working immediately, so update your server-side tracker secret before relying on authenticated ingestion.The complete replacement token is returned once in
requestAuthToken. MCP equivalent: datafast_bot_traffic_token_rotate, with confirm: true required.Related: Get token status · Bot traffic tracking
Request
Path parameters
websiteIdstring
required
Website ObjectId used by account tokens to choose which website to query or manage. Website ObjectId. Get it from the dashboard or the List websites API.
Response
Returns a JSON object with
status: "success" and endpoint-specific fields in data (and pagination when the endpoint is paginated).Response fields
data[].websiteIdstring
Website ObjectId used by account tokens to choose which website to query or manage.
data[].domainstring
Tracked domain.
data[].hasTokenboolean
Whether a request-authentication token exists.
data[].displayTokenstring|null
Masked token display value, never the secret.
data[].createdAtstring|null
When the current token was created.
data[].requireAuthTokenboolean
Whether incoming Bot traffic requests must include the token.
data[].requestAuthTokenstring
Full replacement token. Returned once; store it immediately.
Authentication
Requires an owner
dft_ account token with settings:write. Website API keys (df_) cannot call this endpoint.The token must be allowed to access the website in the path, and that website must belong to the token owner.
The account must have active DataFast API access. Read authentication and scopes for token creation and permissions.
Errors
400 — Invalid website ID.
404 — Website not found, owner access is missing, or no token exists yet.
409 — The token changed during rotation; refresh and try again.
See API errors for the standard error envelope, auth failures, validation errors, permission errors, and rate limits.