A valid request URL is required to generate request examples{
"waitlists": [
{
"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"
}
}My early access requests
Which feature queues this contact is in, and where each request stands. What a “request access” button renders: whether they already asked, how many people are ahead of them, and whether it has been granted.
This is not the environment’s own waitlist. That one is a door — while it holds, nobody through it gets a session at all (POST /v1/waitlist). A feature queue is a request: it is joined by somebody who is already signed in, and it never affects their ability to sign in.
position is null on a granted request, and the null is a statement rather than a missing number — there is no place in a line somebody has already left.
An anonymous session answers 200 with an empty list rather than a refusal, for the reason GET /v1/contact/checklist does: the widget runs on pages where nobody has signed in yet, and a console error is the wrong way to say “there is nothing here for you”.
A valid request URL is required to generate request examples{
"waitlists": [
{
"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"
}
}