How to connect Zoho Books

Connecting Zoho Books takes two actions: authorize the connection with your Zoho account, then select which Zoho Books organization the connection should use. There are no credentials to copy and paste — Apideck handles the OAuth flow, and it also refreshes the access token for you afterwards, so the connection keeps working without you re-entering anything.

Prerequisites

• An active Zoho Books account with at least one organization.
• Organization-level access in the Zoho Books organization you want to connect. Zoho requires organization-level access to authorize a third-party connection, so sign in with an account that has it in that organization.
• If you work with several organizations, know which one this connection is for. A connection serves one organization (see Connecting more than one organization).

To check which organizations your account can reach, click the Organization Name in the top-right corner of Zoho Books and select Manage — see Zoho's Manage Multiple Organizations article.

1. Start the authorization

1. Open the Zoho Books connection in Vault.
2. Click Authorize. You are redirected to Zoho to sign in.

You do not need to pick a Zoho data center. Zoho runs region-specific data centers (US, EU, IN, AU, JP, CA, SA), and the correct one for your account is detected during authorization.

2. Sign in and approve access

1. Sign in with the Zoho account that has access to the organization you are connecting.
2. Review the consent screen and approve the requested access.

The consent screen names the application requesting access — that is the application belonging to the provider whose integration you are setting up, or Apideck when the integration uses Apideck's shared credentials.

What is requested depends on how that provider configured the integration: it may be full access to Zoho Books, or a narrower per-area set of read and write permissions. The consent screen is the accurate list for your case, so read it before approving. If the access shown is wider than you expect, raise it with the provider before continuing rather than approving and reversing it later.

Complete the flow in one sitting. Zoho's authorization code is single-use and valid for only a couple of minutes, so if you stop partway, close the tab, or the redirect is interrupted, return to Vault and click Authorize again.

3. Select your Organization ID

After Zoho redirects you back to Vault, an Organization ID dropdown appears. Its options are fetched live from your Zoho account, so it lists the organizations the account you just authorized with can actually reach.

1. Select the organization this connection should use.
2. Click Save.

This step is required. Organization ID has no default: until you select one and save, the connection is not marked Connected, and requests through it will not return data.

You are never asked for an API domain or an accounts server. Both are resolved automatically from the authorization, which is also how the region detection in step 1 works.

Once the organization is saved and the connection shows Connected, Zoho Books is connected.

Connecting more than one organization

Each Zoho Books organization needs its own authorization and its own connection — one connection cannot span two organizations, and changing the selected organization repoints the existing connection rather than adding one. To connect a second organization, create another Zoho Books connection and run steps 1–3 again, selecting that organization in step 3.

Notes

• Token refresh is automatic. Apideck refreshes the short-lived access token for you. There is no expiry date to diary and nothing to re-enter.
• Avoid re-authorizing repeatedly. Zoho stores a limited number of active authorizations per user (20). Every fresh authorization creates one, and once the limit is passed Zoho silently drops the oldest — which can break a connection you set up long ago, including one for a different organization. Re-authorize when you need to, but not as a routine first troubleshooting step.
• Your access governs the connection's access. If your Zoho Books access to the selected organization is reduced or removed later, the connection loses that access too.

Revoking access

You can revoke the connection from the Zoho side at any time:

1. Go to accounts.zoho.com and open your account's security settings.
2. Find the section listing third-party applications with access to your account (Zoho has named it Authorized Websites or Connected Apps depending on the account version).
3. Select the application you want to remove and revoke its access.

Zoho documents the current steps in How do I revoke third-party access to my Zoho account?.

After revoking, the connection stops returning data. To reconnect, open the connection in Vault, click Authorize again, and confirm the Organization ID selection.

Troubleshooting

The connection still shows "Not Connected" after I authorized. The Organization ID is almost certainly not saved yet — authorization alone does not complete the connection. Open the connection, select your organization, and click Save.

The Organization ID dropdown is empty. Work through these in order:

1. Confirm the Zoho account you authorized with has at least one Zoho Books organization — check via Organization Name > Manage in Zoho Books.
2. Confirm that account has organization-level access to it. An account that cannot open the organization in Zoho Books will not see it listed here.
3. If both hold, the dropdown is populated by reading your Zoho Books settings, and the integration's approved permissions may not include that. That is configured by the provider who set up the integration, so report it to them — or to Apideck Support — rather than re-authorizing.

Authorization failed partway, or Zoho reported an invalid or expired code. The authorization code is single-use and short-lived. Start again from Vault with Authorize and complete sign-in and consent without pausing.

The connection works, but returns another organization's data. Check which organization is selected in the Organization ID dropdown. A connection reads from exactly the organization saved there.

The connection worked and later stopped. The usual causes, in order: access was revoked in the security settings of the Zoho account that authorized it (see Revoking access above); that user's access to the organization was reduced or removed; or the stored authorization was displaced by Zoho's per-user authorization limit (see Notes). In all three cases, re-authorizing the connection and re-confirming the organization restores it — with the access of whoever authorizes it.

Still stuck? Contact Apideck Support.