Reference · built on requestConnectorERP & finance

Zoho Books

Invoices, bills, contacts, expenses, and bank transactions from Zoho Books organizations through API v3 with OAuth 2.0 scopes.

Request accessPricing ↗

About

Zoho Books is Zoho's online accounting application. API v3 has a root endpoint per data center, https://www.zohoapis.com/books/v3 for the .com region, and every request names the organization with organization_id. Modules cover Contacts, Estimates, Invoices, Customer Payments, Bills, Vendor Payments, Expenses, Items, Bank Accounts, Bank Transactions, Journals, and Projects. Access is granted per scope in the form ZohoBooks.<module>.<operation>, for example ZohoBooks.invoices.READ.

An operator on Fibric reads the modules its scopes allow, watches records through workflow-rule webhooks, and proposes invoice actions or payments for your approval. Every action is recorded with what changed, why, and how to put it back.

This is a reference listing. It documents what Fibric would read from Zoho Books and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Invoices, Estimates, Recurring Invoices, Credit Notes, and Customer Payments
  • Bills, Vendor Payments, Vendor Credits, and Expenses
  • Bank Accounts, Bank Transactions, and Journals
  • Contacts (customers and vendors) under the ZohoBooks.contacts scope; Items, Taxes, and Users under ZohoBooks.settings
  • List responses paged through page_context: page, per_page, and has_more_page, 200 items by default
  • Workflow-rule webhooks that POST, PUT, or DELETE to your URL when the chosen event occurs, secured with a secret token

Proposed actions

  • Target capability: propose creating or updating an invoice, then emailing it or marking it as sent
  • Target capability: propose approving, voiding, or writing off an invoice
  • Target capability: propose creating a customer payment against open invoices

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Send reminders that match the ledger

    Read overdue invoices and customer balances and propose the next reminder, with the invoice list, for a person to send.

    With Dunning Cadence

  • Hold orders for customers over their limit

    Read open invoices and payments per contact, compare with the credit terms you set, and propose a hold before the next estimate converts.

    With Credit Hold, Quote to Order

  • Check expenses against policy before they post

    Read new expense records and their receipts and propose approve, query, or reject with the policy line cited.

    With Expense Policy

  • Match bills to what arrived

    Read bills and purchase records, compare quantities and amounts, and propose a hold on any bill that does not match.

    With Three-Way Match

Requirements

  • A Zoho Books organization and its organization_id from GET /organizations
  • A client registered in the Zoho API console; a Self Client if the integration has no web UI
  • access_type=offline at consent so a refresh token is issued; access tokens expire after one hour
  • The data-center domain of the organization (.com, .eu, .in, .com.au, .jp, .ca, .sa, .com.cn) for both the accounts and API hosts
Authentication
OAuth 2.0 through accounts.zoho.com with scopes in the form ZohoBooks.<module>.<operation>; a Self Client grant suits server-side jobs with no redirect URL.

Limits

  • 100 requests per minute per organization; daily caps by plan from 1,000 on Free to 10,000 on Premium, Elite, and Ultimate
  • Concurrent calls: 5 on the Free plan, 10 on paid plans as a soft limit; 429 with code 44 or 45 when exceeded
  • At most 15 active access tokens per refresh token; the 16th request invalidates the oldest
  • Webhooks are configured per workflow rule in the Zoho Books settings, not created through API v3

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Zoho Books ↗

Questions and answers

Which host do I call?
The one for your data center. The root endpoint is https://www.zohoapis.com/books/v3; replace .com with .eu, .in, .com.au, .jp, .ca, .sa, or .com.cn as appropriate. The api_domain value in the token response tells you which one to use.
How are scopes written?
As service_name.scope_name.operation_type, where the operation is CREATE, READ, UPDATE, DELETE, or ALL. For example ZohoBooks.invoices.READ reads invoices and ZohoBooks.contacts.ALL covers customers and vendors. An access token is valid only for the operations in its scope.
Does Zoho Books send webhooks?
Yes, as a workflow action. Create a webhook under Settings, Automation, Workflow Actions with your URL, method, parameters, and headers, optionally secured with a 12–50 character secret token, then attach it to a workflow rule for the module and event.
Ask about Zoho Books

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Zoho Books through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy