Get safety rules
BillionSend extension: who may write in, screening, code extraction, what the inbox may send and where it forwards.
/inboxes/{inbox_id}/safetyAuthorizationBearer 令牌 · header必填A BillionSend API key (bs_…).
inbox_idstring必填The inbox ID or its email address, such as support@example.com
Safety rules
objectstring必填inbox_safetyinbox_idstring<uuid>必填accept_fromstring必填Who may write in: anyone; verified (DMARC-aligned senders, known threads, the allowlist); allowlist only. Mail that fails is quarantined.
anyoneverifiedallowlistallowliststring[]必填"local@domain" (exact) or "*@domain" (the domain and its subdomains). On the shared domain it only lets mail in
owner_addressesstring[]必填Owners besides the team members' login addresses; ignored on the shared domain
screeningboolean必填Score external mail for prompt injection (agent inboxes only)
extract_codesboolean必填Expose extracted codes and sign-in links
send_policystring必填What 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_approvalboolean必填Every send waits for a person
private_codesboolean必填Received codes and sign-in links can't be sent on to anyone but owners
send_capinteger | null必填Unattended recipients per UTC day; null: no cap. 1-50 on the shared domain
forward_tostring[]必填Forward every delivered message to these team member or owner addresses; team members only on the shared domain
Missing, malformed, unknown or revoked API key
statusCodenumber必填namestring必填messagestring必填Not found
statusCodenumber必填namestring必填messagestring必填Over the rate limit (rate_limit_exceeded, with Retry-After)
statusCodenumber必填namestring必填messagestring必填