--- title: "Fetch Items from NoSQL Table" url: https://docs.catalyst.zoho.com/en/sdk/javascript/v1/cloudscale/nosql/fetch-items/ description: "This page describes the method to perform operations in the NoSQL component." last_updated: 2026-09-09T10:45:38Z service: CloudScale type: general related_links: - name: "Catalyst CloudScale" url: /en/cloud-scale/ - name: "NoSQL Help Documentation" url: /en/cloud-scale/help/nosql/introduction/ - name: "Java SDK Documentation" url: /en/sdk/java/v1/cloud-scale/nosql/fetch-items/ - name: "Python SDK Documentation" url: /en/sdk/python/v1/cloud-scale/nosql/fetch-items/ - name: "REST API Documentation" url: /en/api/code-reference/cloud-scale/nosql/fetch-item/#FetchItem repository: name: "Repository" url: https://github.com/catalystbyzoho/zcatalyst-sdk-js --- # Fetch Items from NoSQL Table > **Note:** Ensure you have installed the [required package](https://docs.catalyst.zoho.com/en/sdk/javascript/v1/cloudscale/nosql/overview/#prerequisites) to use this SDK method. Using the `fetchItem()` SDK method, you can fetch the required items from a NoSQL table. The items can be referred using their [Primary Keys](https://docs.catalyst.zoho.com/en/cloud-scale/help/nosql/components/#table-keys). For example, you can use just the partition key or a combination of the partition key and sort key to fetch the item. Optionally, you can filter the attributes to be fetched by specifying the required attributes. > **Note:** Catalyst enables you to fetch a **maximum of 100 items** from a NoSQL table in a single SDK read operation. The following example code snippet details the following logic: * The required item is being identified using its **partition key**: `fruit` whose value is "`apple`". * Specific attributes such as `properties` and taste are filtered to be fetched using `required_attributes`. * Implements `consistent_read` to indicate if the read operation must be done using the master or a slave cluster. - If the value is set as `true`, it is queried from the master. - If the value is set as `false`, it is queried from the slave. > **Note:** In the master-slave replication, the master contains all the data of the database, and the slave contains copies from the master. Performing a read operation from the slave can reduce the overall cost with the trade-off being a minor delay in the updated data being reflected. ```javascript //Fetch properties of a NoSQLItem identified with the partition key value "apple" const fetchedItem = await table.fetchItem({ // Define the partition key and value of the item to be fetched keys: [new NoSQLItem().addString('fruit', 'apple')], // Set consistent_read to true to query from master. If set to false, it is queried from slave. consistent_read: true, // Specify the attributes to be fetched required_attributes: [['properties', 'taste']] }); ```