Some operations via the Routable API will trigger emails on your behalf to customers.
To give these emails a human look and feel, we include the name and avatar of a member from your team on the outbound email.
This is why we have the
requester field on our requests and you can find a list of eligible requesters via the List Memberships endpoint.
Are these safe to cache?
Most teams in production identify a member of their finance team that they would like emails to come from and cache this ID in production and use it across all their requests.
Updated 4 months ago