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 purchasereceives API

PurchaseReceives Module

Zoho Inventory purchasereceives 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 purchasereceives. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 1 JSON Schema.

This API exposes 8 operations across 6 paths, and defines 49 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.

8 operations 6 paths 49 schemas 1 DELETE1 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 purchasereceives API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (Zoho_Auth) using the implicit flow, exposing 4 scopes.

Paths & Operations 8

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

purchasereceives 8

PurchaseReceives Module

POST
/purchasereceives
Create a purchase receive
create_purchase_receive 1 param body → 201
GET
/purchasereceives/{purchasereceive_id}
Retrieve a Purchase Receive
get_purchase_receive 2 params → 200
PUT
/purchasereceives/{purchasereceive_id}
Update a Purchase Receive
update_purchase_receive 3 params body → 200
DELETE
/purchasereceives/{purchasereceive_id}
Delete a Purchase Receive
delete_purchase_receive 2 params → 200
POST
/purchasereceives/{purchasereceive_id}/submit
Submit a purchase receive for approval
submit_purchasereceive 2 params → 200
POST
/purchasereceives/{purchasereceive_id}/approve
Approve a purchase receive
approve_purchasereceive 2 params → 200
POST
/purchasereceives/{purchasereceive_id}/approve/final
Final approval of a purchase receive
approve_purchasereceive_final 2 params → 200
POST
/purchasereceives/{purchasereceive_id}/reject
Reject a purchase receive
reject_purchasereceive 2 params body → 200

Schemas 49

The contract defines 49 schemas that model the data the API accepts and returns. The most detailed are purchase_receive-response (15 properties), create-a-purchase-receive-request (5 properties), update-a-purchase-receive-request (5 properties), create-a-purchase-receive-response (3 properties). Each schema is shown below with its type and property counts.

contact_person_id
string
Unique ID generated by the server for the contact person
delete-a-purchase-receive-response
object
2 properties
vendor_id
string
Unique ID generated by the server for the vendor.
fax
string
Fax number of the customer's billing address.
city
string
Name of the city of the customer's billing address.
label
string
Label of the Custom Field
country
string
Name of the country of the customer's billing address.
purchaseorder_number
string
Purchase Order number.
value
string
Value of the Custom Field
last_modified_time
string
Time at which the Purchase Order details were last modified.
created_time
string
Time at which the Purchase Receive was created.
purchase_receive-response
object
15 properties
description
string
Description of the line item.
state
string
Name of the state of the customer's billing address.
receive_id
string
Unique ID generated by the server for the Purchase Receive. This is used as identifier.
shipping_address
array
Customer's shipping address. It contains - address , city , state , zip , country and fax .
create-a-purchase-receive-request
object
5 properties 2 required
billing_address
array
Customer's billing address. It contains - address , city , state , zip , country and fax .
item_id
string
Unique ID generated by the server for the item. This is used as an identifier.
custom_fields
array
Custom fields for a purchasereceive.
reject-request
object
1 property
item_order
integer
The order of the line items, starts from 0 by default.
address
string
Name of the street of the customer's billing address.
receive_number
string
Number of the Purchase Receive.
quantity
number
Quantity of the line item.
name
string
Name of the line item.
vendor_name
string
Name of the vendor.
unit
string
Unit of line item.
date
string
Date of Purchase Receive
customfield_id
string
Unique identifier of the custom field
retrieve-a-purchase-receive-response
object
3 properties
batches-update
array
Batches for the line item. Create a new batch using batchnumber or reference an existing batch using batchid . Applicable only for items with batch tracking en…
create-a-purchase-receive-response
object
3 properties
line_items
array
Number of line items for purchase receive. Each line item contains lineitemid , itemid , name , description , itemorder , quantity and unit .
zip
string
Zip code of the customer's billing address.
storages
array
Bin/storage locations allocated for the line item. Applicable only for items with bin tracking enabled.
storages-update
array
Bin/storage locations allocated for the line item. Applicable only for items with bin tracking enabled.
batches
array
Batches for the line item. Create a new batch using batchnumber or reference an existing batch using batchid . Applicable only for items with batch tracking en…
approval-action-response
object
2 properties
update-a-purchase-receive-response
object
3 properties
contact_persons
array
Array of contact person IDs.
serial_numbers
array
Serial numbers for the line item. Applicable only for items with serial tracking enabled.
update-a-purchase-receive-request
object
5 properties 2 required
notes
string
Purchase Receive notes.
purchaseorder_id
string
Unique ID generated by the server for the Purchase Order.
line_item_id
string
Unique ID generated by the server for each line item. This is used as an identifier.
batches-response
array
Batches tracked for the line item. Returned for items with batch tracking enabled.
item_custom_fields
array
List of custom fields associated with the line item
storages-response
array
Bin/storage locations tracked for the line item. Returned for items with bin tracking enabled.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoho-inventory-purchasereceives-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 items API
Where this information came from

This is an independent, third-party profile of Zoho Inventory purchasereceives 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.