Create a new priority

post

https://priorityprotect-api.datadome.co/v1/priorities

Creates a new priority with the provided configuration.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Payload used to create a new priority.

name

string

required

length ≤ 120

Descriptive name of the priority, used for identification in the dashboard and API. Not shown to end users.

maximumConcurrentVisitors

integer

required

≥ 0

Maximum number of concurrent visitors allowed on your website before new visitors are placed in the waiting room.

inactivityTimeoutMinutes

integer

10 to 30

Defaults to 15

How long a visitor can be inactive before their session expires. Every interaction matching the waiting room scope will automatically reset this countdown. Must be between 10 and 30 minutes.

admissionRatePerMinute

integer

required

≥ 0

Maximum number of visitors allowed to leave the waiting room and access the website each minute. This smooths traffic bursts and prevents thundering herd effects when the queue opens.

priority

integer

≥ 0

Determines order of evaluation when multiple priorities could apply. Lower values take precedence.

matchingCondition

string

required

Boolean expression defining which traffic is sent to this priority. Uses DataDome Lucene syntax with AND, OR, NOT operators and field:value matching.

Examples:

domain:www.example.com AND url:/product/*
domain:*
(countrycode:US OR countrycode:CA) AND url:/sale
domain:shop.example.com AND NOT method:GET

preAdmission

object

Pre-admission configuration. If durationMinutes is greater than 0, the pre-admission is active and opens that many minutes before startAt. If durationMinutes is 0, no pre-admission is used.

startAt

date-time | null

UTC timestamp when the priority becomes active (inclusive). ISO 8601 format.

endAt

date-time | null

UTC timestamp when the priority expires and stops accepting visitors (exclusive). ISO 8601 format.

enforceClientSideValidation

boolean

Defaults to true

When true, visitors passing through the queue must successfully execute client-side validation logic in their browser before being granted access to the protected website.

allowAIAgent

boolean

Defaults to false

When true, known AI or automated agents are allowed to bypass the waiting room.

directAccessTrafficType

array of strings

Traffic categories allowed to skip the waiting room entirely. Subset of verifiedBots, customRules. An empty array means no category bypasses.

POST: optional; [], ["verifiedBots"], ["customRules"] or ["verifiedBots","customRules"] are accepted. Omitted defaults to []. Explicit null or unknown values return 400.

PATCH: omit the field to leave the current set untouched. Provide [] to clear it or a subset to replace it. null returns 400.

directAccessTrafficType

Allowed:

isEnabled

boolean

Defaults to true

When true, the priority is active and is triggered if configuration conditions are met. When false, the priority is never triggered.

templateId

uuid | null

Optional template ID (UUID) to associate a waiting room HTML template. Omit or set to null to use no template.

Responses

201Successfully created priority.

400Bad request - malformed JSON or invalid field types.

401Unauthorized - missing or invalid API key.

403Forbidden. The provided API key is valid, but the user does not have sufficient permissions to perform this operation.