Minox – Configuration Guide
Dutch cloud bookkeeping/accounting platform.
How to get OAuth credentials for Minox
Minox issues OAuth clients to software vendors through its open API program. You request access once as the integrating vendor. Minox then sends you a Client ID and Client Secret, and your customers use them to connect their own Minox administrations through Apideck Vault.
Before you start, you'll need:
- An Apideck account with the Accounting API enabled.
- Your company details, ready for the Minox application form.
1. Request open API access from Minox
Fill in the Minox open API application form as the software vendor. Your customers can't request access themselves; the request has to come from you.
When the form asks for a redirect (callback) URL, enter:
https://unify.apideck.com/vault/callback
Minox reviews each application. Once it's approved, Minox sends you the OAuth client credentials and instructions. If you need a timeline, ask Minox through the support contacts below.
2. Receive your Client ID and Client Secret
When Minox approves your application, you receive:
- Client ID
- Client Secret
Keep the Client Secret confidential. Apideck uses it to exchange authorization codes for tokens and to refresh access tokens. Minox access tokens last about one hour, and Apideck refreshes them automatically, so you never handle tokens yourself.
3. Add the credentials in the Apideck Dashboard
- Open the Apideck Minox connector settings.
- Under Use your own client credentials, paste the Client ID and Client Secret from Minox.
- Save the settings.
You need your own OAuth client from Minox before any of your customers can connect. When they do, the main user (hoofdgebruiker) of their Minox subscription signs in and approves the connection.
4. Scopes
Minox controls access with granular resource:read / resource:write scopes. When a customer authorizes, Apideck requests the full accounting scope set up front:
| Area | Scopes |
|---|---|
| Administrations | administration:read |
| Customers and suppliers | customer:read, customer:write, supplier:read, supplier:write |
| Ledger accounts, journals and VAT | ledger_account:read, ledger_account:write, journal:read, journal:write, vat:read |
| Transactions | transaction:read, transaction:write |
| Items | item:read, item:write |
| Cost centers | cost_center:read, cost_center:write |
| Documents (attachments) | document:read, document:write |
| Reports | report:read, profitlossbalance:read |
If Minox asks which scopes your integration needs, request this full set so that every supported resource can work.
5. Redirect URL
The redirect URL registered with Minox must be exactly:
https://unify.apideck.com/vault/callback
If you didn't include it in your application, or you entered a different value, ask Minox to update your OAuth client. Authorization fails when the redirect URL doesn't match.
6. Test with a Minox demo account
To test your integration, create a free Minox demo account at app.minox.nl and request API access for it through the same application form as in step 1.
For the endpoints and fields behind the connector, see the official Minox REST API documentation.
FAQ and troubleshooting
Who do I contact about my application or my OAuth client? Contact Minox API support at api-support@minox.nl or through klanten.minox.nl/support. Minox aims to answer within one business day.
Authorization fails with a redirect URI error.
The redirect URL registered with Minox must be exactly https://unify.apideck.com/vault/callback. Ask Minox API support to correct it if needed.
Something else isn't working. Contact Apideck Support.