How to connect to MYOB

MYOB connects over OAuth 2.0: you sign in with your normal MYOB login, approve access, and then pick which company file the connection should use. There are no credentials to look up or paste — no API key, no client id. The only thing you choose is the company file, and the whole connection takes a couple of minutes.

MYOB Business was previously called MYOB Essentials, and AccountRight company files work here too. You may see any of those names on your account and on the sign-in screens.

Prerequisites

An active MYOB Business subscription (AccountRight is also supported). If you do not have one yet, MYOB offers a free trial — see MYOB pricing.
Your MYOB login — the same email and password you use to sign in to MYOB Business or AccountRight. MYOB never lets an application collect this itself; you always type it on MYOB's own secure.myob.com sign-in page.
Access to the company file you want to connect. You can be the account holder or any user with access to that file. The connection can only reach the data your login can reach.

Decide up front which company file you are connecting. You select it during setup, and each company file needs its own connection.

Steps

Open the integration settings in the application you are connecting from and start the MYOB connection. This opens Apideck Vault.
Click Authorize. Vault redirects you to MYOB at secure.myob.com.
Sign in with your MYOB email and password, and complete two-factor verification if your account uses it.
Review the access being requested and approve it. MYOB asks for permission to access your company files on your behalf. The consent screen shows the name of the application you are connecting from, or "Apideck" if that application is still using Apideck's shared test credentials — either is expected.
MYOB sends you back to Apideck.
Select your Company File. This step is required. The Company File dropdown is populated live from MYOB using the authorization you just completed, so it lists the files your login can open, by name. Pick the one you want this connection to use and save the connection.

Once the company file is selected, the connection is ready. Everything else the connection needs is already in place.

Notes

The Company File selection is not optional. Until a file is chosen, the connection has no target to read from or write to. If the dropdown is empty, see Troubleshooting below.
One connection per company file. A connection points at exactly one company file. If you run several company files in MYOB and want all of them synced, create a separate connection for each and select a different file in each one.
You will not be asked to reauthorize repeatedly. MYOB access tokens are valid for 20 minutes; Apideck refreshes them automatically in the background, and adds the API headers MYOB requires on every call. There is nothing for you to renew or maintain.
The connection works with real data in the file you select. If you are still testing, point the connection at a trial or test company file rather than the one your business runs on.
You can disconnect at any time. Disconnecting the connection in Vault discards the stored tokens and stops all access to the company file. To connect again later, authorize again and reselect the company file.

Troubleshooting

The list comes from MYOB and only contains files the login you authorized with can open. Check that:

You signed in with the MYOB login that has access to that company file — not a different personal or admin account. If you signed in with the wrong one, disconnect and authorize again.
Your MYOB subscription is active. Access has to be live for MYOB to return the file.
The file is online. AccountRight files kept only in a local library on your own computer or a network drive are not reachable by a cloud integration — the file has to be online in MYOB. See MYOB's company files documentation.

If the file is online, your subscription is active, and you still cannot see it, contact Apideck Support.

I selected the wrong company file

Open the connection's settings and change the Company File selection to the correct file. If data had already synced from the previous file, ask the team whose application you are connecting from how they want to handle what was already imported — that data lives on their side, not in MYOB.

You see an error about the redirect URI, or the browser stalls on the MYOB screen instead of returning. This is a configuration issue on the application side, not something you can fix from your account. Report it to the team whose application you are connecting from.

"Access denied" or a permissions error right after approving

The authorization was declined, or the login you used cannot reach the company files you expected. Retry, click all the way through the approval screen, and make sure you are signed in with a login that can open the file in MYOB.

The connection was working and now fails

Open the connection in Vault and Reauthorize, then confirm the same company file is still selected. If it keeps failing, check with MYOB that your subscription and your access to that company file are both still active.

Still stuck

For anything about your MYOB login, subscription, or access to a company file — including removing an application's access from the MYOB side — contact MYOB support through your MYOB account. For anything on the Apideck side of the connection, contact Apideck Support.

Reference

MYOB — sign in and check your subscription
MYOB authentication documentation — the sign-in and consent flow behind this connection
MYOB company files documentation — how MYOB exposes company files