Get safety rules
BillionSend extension: who may write in, screening, code extraction, what the inbox may send and where it forwards.
/inboxes/{inbox_id}/safetyAuthorizationToken Bearer · headerobligatorioA BillionSend API key (bs_…).
inbox_idstringobligatorioThe inbox ID or its email address, such as support@example.com
Safety rules
objectstringobligatorioinbox_safetyinbox_idstring<uuid>obligatorioaccept_fromstringobligatorioWho may write in: anyone; verified (DMARC-aligned senders, known threads, the allowlist); allowlist only. Mail that fails is quarantined.
anyoneverifiedallowlistallowliststring[]obligatorio"local@domain" (exact) or "*@domain" (the domain and its subdomains). On the shared domain it only lets mail in
owner_addressesstring[]obligatorioOwners besides the team members' login addresses; ignored on the shared domain
screeningbooleanobligatorioScore external mail for prompt injection (agent inboxes only)
extract_codesbooleanobligatorioExpose extracted codes and sign-in links
send_policystringobligatorioWhat the inbox may send without a person's approval. On the shared domain "allowlist" answers 422, and so does "open" unless the team is on a paid plan and past its first sends
reply_onlyallowlistopenrequire_approvalbooleanobligatorioEvery send waits for a person
private_codesbooleanobligatorioReceived codes and sign-in links can't be sent on to anyone but owners
send_capinteger | nullobligatorioUnattended recipients per UTC day; null: no cap. 1-50 on the shared domain
forward_tostring[]obligatorioForward every delivered message to these team member or owner addresses; team members only on the shared domain
Missing, malformed, unknown or revoked API key
statusCodenumberobligatorionamestringobligatoriomessagestringobligatorioNot found
statusCodenumberobligatorionamestringobligatoriomessagestringobligatorioOver the rate limit (rate_limit_exceeded, with Retry-After)
statusCodenumberobligatorionamestringobligatoriomessagestringobligatorio