Getting access and support

Mapier is in preview. Several things the API cannot do for you yet — issuing a credential, provisioning a connector, turning a capability on — are done by a person, and this page is how you reach one.

Email

Include the following where it applies. Every one of them is something the team would otherwise have to ask you for:

• The account the request concerns, if you have more than one.
• The commandId and Idempotency-Key of any command you are asking about, and roughly when you sent it. Both appear in the 202 response body.
• The errorCode and the full settlement event, if the stream gave you one.
• For a delivery problem: the target you addressed, and whether handle.check reported it reachable.

What to ask for

An account and a connector

Access is not self-serve. Ask for an account and a Mac connector to be provisioned; you will be issued a key and the base URL it is valid against. The quickstart picks up from there.

A capability you do not have

Capabilities are granted per account, and a command you have no capability for fails rather than degrading. Name the capability string from the error and what you are trying to build.

A 503 that does not clear

connector_unavailable means your Mac connector 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

There is no self-service rotation yet. 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 failed settlement with a 4xx-shaped errorCode. 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, rich links and polls all degrade differently by receiving client; the message guides cover which.