Authentication

HTTP Authentication, scheme: Bearer

The MassPay API uses API keys to allow access to the API. You can register a new MassPay API key at our developer portal.

Do not share your secret API keys in publicly accessible areas such as GitHub, BitBucket, Open Source projects or client scripts.

MassPay API expects for the API key to be included in all API requests to the server in a header that looks like the following:

Authorization: Bearer API_KEY

📘
You must replace API_KEY with your personal API key.

🚧
A new API key is not valid instantly
A key returned by Create business or by the dashboard becomes usable a few seconds after it is returned, in rare cases a few minutes. Until then, every request made with it fails with 403 Forbidden and the body {"message":"Forbidden"}. Retry with a short backoff for up to a minute before treating a 403 as a permissions problem, and store the key when you receive it: it is not returned again.

Authentication

You must replace API_KEY with your personal API key.

A new API key is not valid instantly

You must replace `API_KEY` with your personal API key.