List where a newsletter's events go

Every destination this newsletter's published events are delivered to, newest first. Needs webhooks: read.

A destination is not necessarily an HTTPS endpoint. It can also be a queue, a stream or an object store, for a consumer that would rather not run a web server. type says which kind this one is.

Read only. Destinations are added, edited and disabled in the delivery portal, and POST /newsletters/{newsletter}/portal-session mints the link to it.

A newsletter that has never opened that portal has no destinations and answers with an empty page, which is different from an error: an event published by a newsletter with no destinations is accepted, recorded and delivered nowhere.

Nothing a destination authenticates with is returned, including the secret its deliveries are signed with and any request header the creator configured on it. target is a display summary of where it points, the host of an endpoint or the name of a queue, and it is the identifying detail this operation returns in place of the full configuration. The portal is where the rest of it can be read by the person who set it up.