How to retrieve notes in Zoho CRM

Retrieving notes in Zoho CRM can be done through the UI on individual records or programmatically via the Zoho CRM REST API, depending on your use case. Here at Beam Help — independent expert support for Zoho, not official Zoho support — we walk you through both approaches below.

Why this matters

Notes are one of the most practical ways to track the progress of a sale or customer interaction, giving every team member a running summary of what has happened on a record. ^[2] Whether you need to pull notes for reporting, audit, or display them in a custom widget, knowing the right retrieval method saves significant time. If you are building an integration or automation, the API route is especially important to understand correctly.

Step-by-step

Step 1. Understand what Notes are in Zoho CRM.

Notes act as a summary layer on top of CRM records, letting sales reps document observations about customer and prospect interactions so that deal progress is always visible to the team. ^[8] They can be attached to standard modules such as Leads, Contacts, Accounts, and Deals.

Step 2. Retrieve notes through the Zoho CRM user interface.

Open any record in Zoho CRM (for example, a Contact or Account). Scroll down to the related lists section of the record detail page, where a Notes tab or panel will display all notes associated with that record. ^[1] You can click into any individual note to read its full content.

Step 3. Use the Notes API endpoint to retrieve notes programmatically.

Zoho CRM exposes a dedicated Notes module through its REST API. To fetch notes, you call the standard Get Records endpoint, targeting the Notes module:

GET https://www.zohoapis.com/crm/v8/Notes

Include your OAuth token in the Authorization header as Zoho-oauthtoken <your_token>. ^[6]

Step 4. Authenticate with the correct OAuth scope.

The Notes module retrieval requires admin-level access. If a non-admin user attempts to call the Notes module endpoint, the API returns an HTTP 403 NOT_SUPPORTED error, indicating that only admin users are permitted to fetch records from the Notes module. ^[6] Ensure the OAuth token you are using belongs to, or is generated on behalf of, an admin user.

Step 5. Handle pagination with page_token for large result sets.

When the number of notes is large, the API response will include a page_token value. Pass this token as a query parameter in your next request to retrieve the following page of results. ^[6] For example:

GET https://www.zohoapis.com/crm/v8/Notes?page_token=<token_value>

Continue iterating until no further page_token is returned, which signals you have reached the last page.

Step 6. Filter notes by parent record if needed.

If you only want notes belonging to a specific record (for example, a particular Lead or Contact), use the COQL API to write a targeted query against the Notes module, filtering by the parent record's ID. ^[2] This avoids pulling all notes across the entire CRM and keeps your API calls efficient.

Step 7. View notes via the Zoho FSM extension (if applicable).

If your organisation uses the Zoho FSM extension inside Zoho Desk, notes on linked CRM records can also be surfaced there. Navigate to a Contact or Account record, click the Zoho FSM tab, hover over a linked Request, Estimate, Work Order, Service Appointment, or Asset, and click the View Notes icon. You will be taken directly to the Notes tab for that record. ^[1]

Common pitfalls

• 403 NOT_SUPPORTED error: This is the most common issue when retrieving notes via API. It occurs when the OAuth token in use does not belong to an admin user. Verify the user role and regenerate the token with admin credentials. ^[6]
• Notes visible on desktop but not on mobile/tablet: There are known display inconsistencies where Notes and Attachments related lists appear correctly in the desktop browser but may not render as expected on tablet or mobile versions of Zoho CRM. ^[5] If your team relies on mobile access, test the Notes visibility on each device type.
• Pagination not handled: If you only make a single API call without checking for a page_token in the response, you may silently miss a large portion of your notes data. Always check the response metadata for pagination tokens. ^[6]

What to check

• Confirm that the OAuth token used for API calls belongs to an admin user, since non-admin tokens will be rejected with a 403 error when querying the Notes module. ^[6]
• Verify that the Notes related list is enabled and visible in the module layout for the records you are inspecting in the UI. ^[5]
• If using pagination, ensure your code loops through all page_token values until the final page is reached, so no notes are omitted from your results. ^[6]