A valid request URL is required to generate request examples{
"admitted": 123
}{
"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"
}
}Let people in
Lets people out of one feature queue (waitlist=…, required here). Those people already have accounts, so nothing is attached and no credential is mailed: what it does is record that each contact was let in, per person — which is what a segment condition on the queue reads, and therefore what turns the flag on for them.
Idempotent: an entry already admitted is skipped, so a second call mails nothing.
A valid request URL is required to generate request examples{
"admitted": 123
}{
"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"
}
}Autorizações
A staff session token, uk_st_…. Minted by sign-up, sign-in or the two-factor exchange. Only a 401 means it is spent; not_a_member (403) is about the organization named in X-Organization-Id and leaves the token good for the others.
Parâmetros de consulta
Which environment to act in. A view parameter, valid only on the staff surface — a machine credential never chooses its environment, it is resolved from the key.
live, test Which feature queue to admit from. Required: there is no admitting every queue at once.
^[a-z0-9][a-z0-9._-]{0,79}$Corpo
Everybody still waiting in this queue — launch day, in one call.
The feature's name in the reader's words, for the announcement. Without it the message falls back to the queue's key.
Whether the people let in are emailed. Turn it off when your own product announces the access.
Resposta
How many were let in by this call.