How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zoho Inventory locations API

Locations Module

Zoho Inventory locations API is one of 37 APIs that Zoho Inventory publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Locations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 1 JSON Schema.

This API exposes 10 operations across 7 paths, and defines 39 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://www.zohoapis.com/inventory/v1.

10 operations 7 paths 39 schemas 1 DELETE3 GET5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://www.zohoapis.com/inventory/v1
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Zoho Inventory locations API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (Zoho_Auth) using the implicit flow, exposing 4 scopes.

Paths & Operations 10

Across 7 paths, the API surfaces 10 operations — 1 DELETE, 3 GET, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

locations 10

Locations Module

POST
/settings/locations/enable
Enable Locations
enable_locations 1 param → 200
POST
/locations
Create a location
create_location 1 param body → 201
GET
/locations
List all locations
list_locations 3 params → 200
GET
/locations/{location_id}
Get a location
get_location 2 params → 200
PUT
/locations/{location_id}
Update location
update_location 2 params body → 200
DELETE
/locations/{location_id}
Delete a location
delete_location 2 params → 200
POST
/locations/{location_id}/active
Mark as Active
mark_location_as_active 2 params → 200
POST
/locations/{location_id}/inactive
Mark as Inactive
mark_location_as_inactive 2 params → 200
POST
/locations/{location_id}/markasprimary
Mark as Primary
mark_location_as_primary 2 params → 200
GET
/locations/{location_id}/users
List users of a location
list_users_of_a_location 4 params → 200

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are location-details (24 properties), locations (13 properties), create-a-location-request (11 properties), update-location-request (11 properties). Each schema is shown below with its type and property counts.

autonumbergenerationgroup_id
string
Autonumber generation group ID
attention
string
Attention of the location.
state
string
State Name of the location.
is_primary
boolean
Whether it is primary location or not
type
string
Type of the location
state_code
string
State code of the location.
locations
object
13 properties
get-a-location-response
object
3 properties
associated_series_ids
array
List of associated series IDs
create-a-location-request
object
11 properties 2 required
location-user
object
7 properties
update-location-request
object
11 properties 2 required
user_name
string
User Name
location-details
object
24 properties
location_id
string
Location ID
parent_location_id
string
Parent Location ID
status
Status of the locations. Allowed Values: active , inactive
update-location-response
object
3 properties
enable-location-response
object
2 properties
create-a-location-response
object
3 properties
location_name
string
Name of the location
country
string
Country Name of the location.
phone
string
Mobile number for location
mark-as-inactive-response
object
2 properties
is_all_users_selected
boolean
Whether all users are selected or not
list-all-location-response
object
3 properties
user_ids
string
Comma separated user ids.
delete-a-location-response
object
2 properties
city
string
City Name of the location.
user_id
string
User ID
list-users-of-a-location-response
object
4 properties
street_address1
string
Street Name of the location.
tax_settings_id
string
Tax Settings ID
mark-as-primary-response
object
2 properties
mark-as-active-response
object
2 properties
address
object
7 properties
street_address2
string
Street Name of the location.
page-context
object
6 properties
email
string
Email id for the location

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoho-inventory-locations-api-openapi.yml Raw ↑

Other APIs Zoho Inventory publishes across the network.

Zoho Inventory batches API
Zoho Inventory bills API
Zoho Inventory compositeitems API
Zoho Inventory contact-persons API
Zoho Inventory contacts API
Zoho Inventory credit-notes API
Zoho Inventory currency API
Zoho Inventory customer-payments API
Zoho Inventory delivery-challans API
Zoho Inventory inventoryadjustments API
Zoho Inventory invoices API
Zoho Inventory itemgroups API
Where this information came from

This is an independent, third-party profile of Zoho Inventory locations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.