List sending tools
Each sending tool mailboxes can be exported to, with what connecting an account there takes and the range of each setting.
apiKeyAuthorizationBearer <token>An API key from the Developers page. rhq_test_ keys reach the sandbox, rhq_live_ keys the live side.
Success
application/json- response
Success
data*array<>ranges*curl -X GET "https://example.com/v1/sequencers/platforms"{ "data": [ { "platform": "instantly", "name": "Instantly", "fields": [ { "key": "apiKey", "label": "string", "required": true, "secret": true, "help": "string" } ], "settings": [ { "key": "warmup", "label": "string", "kind": "boolean", "min": 0, "max": 0, "help": "string" } ], "customTracking": true, "removesMailboxes": true } ], "ranges": { "property1": { "min": 0, "max": 0 }, "property2": { "min": 0, "max": 0 } }}Add mailboxes to a domain POST
Orders mailboxes on a connected domain by its id: the same as `POST /v1/mailboxes` naming the domain. The first ones or more later, up to 10 in all. Each month is held from your wallet now and only taken once that mailbox is set up, so one that fails costs nothing. The first mailbox on a domain administers its Google account. Follow `mailbox.active` or poll each mailbox; then read its sign-in details from the credentials route. Send an Idempotency-Key header so a retry never orders twice.
Connect a sending tool POST
Connects your account at a sending tool. We check it with the tool before saving: one it refuses is answered 422 with the reason, and nothing is saved. Keys and passwords are kept sealed by our mailbox platform and never shown again. See `GET /v1/sequencers/platforms` for what each tool needs.