Preview what would actually alert this recipient

Resolves the rules the way delivery does and explains the outcome. Use this before trusting a configuration — it is the only endpoint that answers "who wins" rather than "what is stored". It reads state only and sends nothing.

It answers for two different sends, because there are two. source, steps and resolution describe an alert addressed to THIS PERSON: most specific wins — the personal rule beats a group rule, except that a group rule with override_recipient_settings beats the personal one; when nothing is configured the account-wide default steps apply. group_delivery describes an alert addressed to a GROUP the person belongs to, which is how inbound integrations page people. That path never consults the personal rule at all: the group has either its own rule or the account-wide default, and one decision covers every member. The two sections disagreeing is normal and is exactly what this endpoint exists to show.

Read warnings first. They are the facts that break delivery while every individual field still reads healthy — most often a group that carries the traffic having no rule of its own. delivery.allowed is NOT a verdict on the configuration: it answers only "may an alert go out at this very minute", i.e. quiet hours and the schedule grid. It stays true for a configuration that would reach nobody.