List email providers
Which outbound relays this store has connected, and whether each is switched on. THIS IS THE INFRASTRUCTURE UNDER THE MAIL, not the mail. What the store SENT, the per-event copy and the send log naming each recipient, is the notifications family and a different grant. NO CREDENTIAL IS PUBLISHED AND NONE CAN BE. The stored secret is sealed and is unsealed only for one send; has_secret reports whether one exists and is the whole of what this API will say about it. The provider’s configuration document is not published either: it is free-form text this platform never inspects, so it is where a mispasted credential would sit. THERE IS NO WRITE ON THIS RESOURCE and there will not be. A key able to replace a connection would point every message the store sends, password resets included, at a relay of its choosing, with nothing on the merchant’s side looking different.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Query Parameters
Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
1 <= x <= 100The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.