A valid request URL is required to generate request examples{
"waitlist": "<string>",
"status": "waiting",
"position": 123,
"joined_at": "2023-11-07T05:31:56Z",
"admitted_at": "2023-11-07T05:31:56Z"
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}Ask for early access
Puts this contact in the queue for one feature. key is the key of the feature flag behind that feature, in this environment — a queue with no flag behind it answers 404 unknown_waitlist. That is what a queue is for: early access is granted by pointing that flag at a segment of the people admitted here, and it also keeps the column from being free text written by whoever holds a contact session.
Idempotent: asking twice keeps the first place in line and answers with the state either way, so a client never has to tell “you just joined” from “you were already here”. Nothing is emailed — the person is inside your product looking at the answer; the message worth sending is the admission, and that one your panel sends.
The queue does not exist until somebody joins it, and it is visible in the panel from that moment (GET /v1/organization/waitlist?waitlist=…). Letting people in is done there, and what admission produces is a fact per person — which is what a segment condition on this queue reads, and therefore how the flag turns on.
An anonymous session is refused with 403 not_identified: there is nobody to let in later and no address to tell.
Rate limited to 60 requests an hour per contact session.
A valid request URL is required to generate request examples{
"waitlist": "<string>",
"status": "waiting",
"position": 123,
"joined_at": "2023-11-07T05:31:56Z",
"admitted_at": "2023-11-07T05:31:56Z"
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}Authorizations
A contact session token, uk_ct_…. Belongs to one of the developer's own users, and reads only that user's data.
Path Parameters
The feature queue's key: the key of the feature flag behind it, in this environment. Lower case letters, digits and . _ -, up to 80 characters.
^[a-z0-9][a-z0-9._-]{0,79}$Body
Whatever your own form asked — "what would you use it for". Your questions, not ours, up to 4 KB. A repeat request never overwrites the answers the first one stored.
Response
Where this request stands.
One contact's request for early access to one feature, as that contact sees it.
The queue's key.
waiting, admitted How many people are ahead of them, plus one — counted among those still waiting, so the number moves as the queue is let in. null once the request is granted.