Zoho Inventory

Zoho Inventory is a cloud-based inventory and order management application that lets businesses track stock, manage sales and purchase orders, fulfill and ship packages, and sync inventory across multiple warehouses and sales channels. The Nexla connector reads from and writes to the Zoho Inventory REST API using OAuth2 authentication.

Power end-to-end data operations for your Zoho Inventory API with Nexla. Our bi-directional Zoho Inventory connector is purpose-built for Zoho Inventory, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Zoho Inventory or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Zoho Inventory workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Zoho Inventory credential, you need a Zoho Inventory account, an OAuth access token generated for your Zoho account, and your Zoho Inventory organization ID. Zoho Inventory uses OAuth2 for all API requests, with the token passed in the Authorization header using the Zoho-oauthtoken scheme.

To obtain your Zoho Inventory credentials, follow these steps:

1. Sign in to the Zoho API Console at https://api-console.zoho.com using the Zoho account associated with your Zoho Inventory organization. If your data resides in another region, use the corresponding domain (for example, .eu, .in, or .com.au).

2. Register a client application by clicking Add Client and choosing the client type that fits your integration. After registration, Zoho issues a Client ID and Client Secret, which you should keep confidential.

3. Generate an OAuth access token for your client, requesting the Zoho Inventory scopes required by your use case. Zoho Inventory uses granular scopes per resource, such as ZohoInventory.items.READ, ZohoInventory.contacts.CREATE, ZohoInventory.salesorders.READ, and ZohoInventory.invoices.CREATE. Grant read scopes for source flows and create scopes for destination flows.

4. Exchange the authorization grant for an access token and a refresh token via the Zoho token endpoint. Access tokens are short-lived (typically one hour); use the refresh token to obtain new access tokens as needed.

5. Locate your Organization ID in Zoho Inventory under Settings and the Organizations section. The organization ID is required on every API request and identifies which Zoho Inventory organization the request applies to.

6. Note the region-specific API base URL for your account. Zoho Inventory serves different data centers from different domains, for example https://www.zohoapis.com/inventory/v1 (US), https://www.zohoapis.eu/inventory/v1 (EU), https://www.zohoapis.in/inventory/v1 (India), and https://www.zohoapis.com.au/inventory/v1 (Australia).

The access token is sent in the Authorization header as Zoho-oauthtoken followed by the token value, and the organization ID is sent as a request parameter on every call. For detailed information about registering clients, scopes, token generation, and available endpoints, see the Zoho Inventory API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Base URL	Yes	No	Region-specific Zoho Inventory API base URL, e.g. https://www.zohoapis.com/inventory/v1 (US), .eu, .in, .com.au, etc.
OAuth Access Token	Yes	No	Zoho OAuth2 access token. Sent as the Authorization header value 'Zoho-oauthtoken <token>'.
Organization ID	Yes	No	Zoho Inventory organization_id, required on every request as a query parameter.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter the region-specific Base URL for your Zoho Inventory account, for example https://www.zohoapis.com/inventory/v1. Make sure the domain matches the data center where your Zoho Inventory organization is hosted.

4. Enter your OAuth Access Token in the corresponding field. Nexla sends this token in the Authorization header using the Zoho-oauthtoken scheme for all API requests to Zoho Inventory.

5. Enter your Organization ID in the corresponding field. This value identifies your Zoho Inventory organization and is sent as a request parameter on every call.

   Zoho OAuth access tokens are short-lived and typically expire after one hour. Use your refresh token to generate a new access token when it expires, and update the credential in Nexla accordingly. Keep your Client Secret, refresh token, and access token confidential.

   For detailed information about OAuth scopes, token generation, organization IDs, and available endpoints, see the Zoho Inventory API documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Zoho Inventory connector tile, then select the credential that will be used to connect to the Zoho Inventory organization, and click Next; or, create a new Zoho Inventory credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Zoho Inventory endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Items

Retrieve items. This endpoint template returns the items (products) in your Zoho Inventory organization, including their names, SKUs, pricing, and stock information.

Requests are scoped to the organization ID configured in your credential. For details about the item object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Item Groups

Retrieve item groups. This endpoint template returns the item groups in your Zoho Inventory organization, which represent sets of related item variants.

Requests are scoped to the organization ID configured in your credential. For details about the item group object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Item Adjustments

Retrieve inventory adjustments. This endpoint template returns the inventory adjustment records in your Zoho Inventory organization, capturing manual changes to stock quantities.

Requests are scoped to the organization ID configured in your credential. For details about inventory adjustments and their fields, see the Zoho Inventory API documentation.

[Rest API] List Contacts

Retrieve contacts. This endpoint template returns the contacts in your Zoho Inventory organization, including both customers and vendors.

Requests are scoped to the organization ID configured in your credential. For details about the contact object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Sales Orders

Retrieve sales orders. This endpoint template returns the sales orders in your Zoho Inventory organization, including their line items, customers, and statuses.

Requests are scoped to the organization ID configured in your credential. For details about the sales order object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Purchase Orders

Retrieve purchase orders. This endpoint template returns the purchase orders in your Zoho Inventory organization, including their line items, vendors, and statuses.

Requests are scoped to the organization ID configured in your credential. For details about the purchase order object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Transfer Orders

Retrieve transfer orders. This endpoint template returns the transfer orders in your Zoho Inventory organization, which move stock between warehouses.

Requests are scoped to the organization ID configured in your credential. For details about the transfer order object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Invoices

Retrieve invoices. This endpoint template returns the invoices in your Zoho Inventory organization, including their line items, customers, and payment statuses.

Requests are scoped to the organization ID configured in your credential. For details about the invoice object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Credit Notes

Retrieve credit notes. This endpoint template returns the credit notes in your Zoho Inventory organization, which record credits issued to customers.

Requests are scoped to the organization ID configured in your credential. For details about the credit note object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Packages

Retrieve packages. This endpoint template returns the packages in your Zoho Inventory organization, representing items grouped for shipment against sales orders.

Requests are scoped to the organization ID configured in your credential. For details about the package object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Warehouses

Retrieve warehouses. This endpoint template returns the warehouses configured in your Zoho Inventory organization, including their locations and settings.

Requests are scoped to the organization ID configured in your credential. For details about the warehouse object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Organizations

Retrieve organizations. This endpoint template returns the Zoho Inventory organizations accessible to your account, which is useful for confirming the organization ID to use in other flows.

For details about the organization object and its fields, see the Zoho Inventory API documentation.

[Rest API] List Users

Retrieve users. This endpoint template returns the users associated with your Zoho Inventory organization, including their roles and status.

Requests are scoped to the organization ID configured in your credential. For details about the user object and its fields, see the Zoho Inventory API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Zoho Inventory data sources can also be manually configured to ingest data from any valid Zoho Inventory API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Zoho Inventory data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Zoho Inventory destination, and select the Send to Destination option from the menu. Select the Zoho Inventory connector from the list of available destination connectors, then select the credential that will be used to connect to the Zoho Inventory organization, and click Next; or, create a new Zoho Inventory credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Zoho Inventory endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Item

Create a new item in Zoho Inventory. This endpoint template creates items using records from a Nexset, sending each record as a separate API request.

Each record must contain the fields required by the Zoho Inventory item object. Requests are scoped to the organization ID configured in your credential. For details about the required fields and request body format, see the Zoho Inventory API documentation.

[Rest API] Create Contact

Create a new contact (customer or vendor) in Zoho Inventory. This endpoint template creates contacts using records from a Nexset, sending each record as a separate API request.

Each record must contain the fields required by the Zoho Inventory contact object. Requests are scoped to the organization ID configured in your credential. For details about the required fields and request body format, see the Zoho Inventory API documentation.

[Rest API] Create Sales Order

Create a new sales order in Zoho Inventory. This endpoint template creates sales orders using records from a Nexset, sending each record as a separate API request.

Each record must contain the fields required by the Zoho Inventory sales order object, including line items and customer references. Requests are scoped to the organization ID configured in your credential. For details about the required fields and request body format, see the Zoho Inventory API documentation.

[Rest API] Create Purchase Order

Create a new purchase order in Zoho Inventory. This endpoint template creates purchase orders using records from a Nexset, sending each record as a separate API request.

Each record must contain the fields required by the Zoho Inventory purchase order object, including line items and vendor references. Requests are scoped to the organization ID configured in your credential. For details about the required fields and request body format, see the Zoho Inventory API documentation.

[Rest API] Create Invoice

Create a new invoice in Zoho Inventory. This endpoint template creates invoices using records from a Nexset, sending each record as a separate API request.

Each record must contain the fields required by the Zoho Inventory invoice object, including line items and customer references. Requests are scoped to the organization ID configured in your credential. For details about the required fields and request body format, see the Zoho Inventory API documentation.

Manual configuration

Zoho Inventory destinations can also be manually configured to send data to any valid Zoho Inventory API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Zoho Inventory APIs expect JSON payloads, and the organization ID must be included as a request parameter on every call. Some Zoho Inventory create endpoints accept the record data as a form-encoded JSONString parameter, so review the endpoint's request format in the Zoho Inventory API documentation when configuring advanced destinations.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Zoho Inventory endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Zoho Inventory endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.