Getting access and support
How to reach the Mapier team for provisioning, a higher ceiling and anything the API cannot tell you itself.
Mapier is in preview. Several things the API cannot do for you yet — provisioning a line, raising a ceiling — are done by a person, and this page is how you reach one.
support@mapier.ai — for everything on this page. There is no ticket portal or status page yet.
Include the following where it applies. Every one of them is something the team would otherwise have to ask you for:
- The project the request concerns, if you have more than one.
- The
commandIdandIdempotency-Keyof any command you are asking about, and roughly when you sent it. - The
errorCodeand the full settlement event, if the stream gave you one. - For a delivery problem: the target you addressed, and whether
POST /v1/handle-checkreported it reachable.
What to ask for
An account and a line
Access is by approval. Registration is closed, and creating an organization — which a test project and its sandbox need as much as a live line does — needs an address Mapier has approved. Book a demo and we will set your account up on the call; an invitation to an organization that already exists needs nothing more. Once you are in, sign in at app.mapier.ai, create a project, and mint a test key yourself — the sandbox needs nobody after that. A live line is a real Apple account on a real device, so it is requested from the project's Lines page and provisioned by our operations team rather than by an instant API call; ask here if a request has been open longer than you expected. The quickstart picks up from the key.
A higher command ceiling
Commands are budgeted per project and environment, and Mapier sets that
ceiling — there is no control for it in the console or the API. Send the
projectId from GET /v1/whoami, the sustained rate and the peak you need in
commands a minute, and what you are building. The ceiling is per project and
environment: live and test each have their own.
Rate limits has the detail.
A 503 that does not clear
503 upstream_unavailable with details.reason: "connector_unavailable", or
503 line_unavailable with relay_down, means your line is not
reachable. It is usually transient and worth
backing off through a few attempts first — but a 503
that persists past a few minutes is one to send in, because nothing you can do
from the API side will clear it.
A key you need to rotate
Create a new key and revoke the old one on the Keys page. If a key has leaked, say so plainly in the subject line — that request gets handled ahead of the queue, and the old key is revoked as part of it.
What this page cannot help with
- A
failedsettlement whoseerrorCodeis in the "fix the request" group. Those are your request, and Handling errors has the taxonomy. Sending them in will only get the same page quoted back. - Message content that arrived but looked wrong. Effects and rich links degrade differently by receiving client; the message guides cover which.