IBM Cloudant Node.js SDK
npm install @ibm-cloud/cloudant
IBM Cloudant Node.js SDK is a client library that interacts with the
IBM Cloudant APIs.
Disclaimer: This library is still a 0.x release. We do consider this
library production-ready and capable, but there are still some
limitations we’re working to resolve, and refinements we want to
deliver. We are working really hard to minimise the disruption from
now until the 1.0 release, but there may still be some changes that
impact applications using this SDK. For now, be sure to pin versions
to avoid surprises.
Table of Contents
- Overview
- Features
- Prerequisites
- Installation
- Using the SDK
* Authentication
* Automatic retries
* Request timeout configuration
* Code examples
* Error handling
* Raw IO
* Further resources
* Browser usage
+ Polyfills
+ CORS
- Questions
- Issues
- Versioning and LTS support
- Open source at IBM
- Contributing
- License
The IBM Cloudant Node.js SDK allows developers to programmatically
interact with IBM Cloudant
with the help of the @ibm-cloud/cloudant package.
The purpose of this Node.js SDK is to wrap most of the HTTP request APIs
provided by Cloudant and supply other functions to ease the usage of Cloudant.
This SDK should make life easier for programmers to do what’s really important
to them: developing software.
Reasons why you should consider using Cloudant Node.js SDK in your
project:
- Supported by IBM Cloudant.
- Server compatibility with:
- IBM Cloudant.
- Apache CouchDB 3.x for data operations.
- Includes all the most popular and latest supported endpoints for
applications.
- Handles the authentication.
- Familiar user experience with IBM Cloud SDKs.
- Flexibility to use either built-in models or byte-based requests and responses for documents.
- Built-in Changes feed follower
- Built-in Pagination (beta)
- Promise based design with asynchronous HTTP requests.
- Use either as native JavaScript or take advantage of TypeScript models.
- Transparently compresses request and response bodies.
- A
Cloudant
service instance or a
CouchDB
server.
- Node.js 20, 22 or 24.
``sh`
npm install @ibm-cloud/cloudant
For fundamental SDK usage information and config options, please see the common IBM Cloud SDK documentation.
This library requires configuration with a service URL and
[Cloudant service credentials][service-credentials] to authenticate with your
account.
There are several ways to set these authentication properties:
1. As environment variables
2. The programmatic approach
3. With an external credentials file
The following section describes the different authentication types and provides environment variable examples.
Examples for other configuration methods are available by following the provided links.
Consult the authentication document
for comprehensive details of all the available authentication methods and how to configure them with environment settings
or programmatically.
Quick start for Cloudant with an IAM API key:
`sh`
CLOUDANT_URL=https://~replace-with-cloudant-host~.cloudantnosqldb.appdomain.cloud # use your own Cloudant public or private URL
CLOUDANT_APIKEY=a1b2c3d4e5f6f1g4h7j3k6l9m2p5q8s1t4v7x0z3 # use your own IAM API key
Quick start for Apache CouchDB with a username/password session:
`sh`
CLOUDANT_AUTH_TYPE=COUCHDB_SESSION
CLOUDANT_URL=https://~replace-with-your-unique-host~.example:6984 # use your CouchDB URL
CLOUDANT_USERNAME=username # replace with your username
CLOUDANT_PASSWORD=password # replace with your password
The SDK supports a generalized retry feature that can automatically retry on common errors.
The automatic retries section has details on how to enable the retries with default values and customize the retries programmatically or with external configuration.
No request timeout is defined, but a 2.5m connect and 2.5m read timeout is set by default. Be sure to set a request timeout appropriate to your application usage and environment.
The request timeout section contains details on how to change the value.
Note: System settings may take precedence over configured timeout values.
Quick start example to list all databases (assumes environment variable authentication):
`js
// section: code
import { CloudantV1 } from '@ibm-cloud/cloudant';
const service = CloudantV1.newInstance({});
service.getAllDbs().then(response => {
console.log(response.result);
});
`
More tutorial examples for creating a database
and document create, read, update and delete operations.
For a complete list of code examples, see the examples directory.
For sample code on handling errors, see
Cloudant API docs.
For endpoints that read or write document content it is possible to bypass
usage of the built-in interface with byte streams.
Depending on the specific SDK operation it may be possible to:
* accept a user-provided byte stream to send to the server as a request body
* return a byte stream of the server response body to the user
Request byte stream can be supplied for NodeJS.ReadableStream or Buffer type parameters
.
For these cases you can pass this byte stream directly to the HTTP request body.
Response byte stream is supported in functions with the suffix of AsStream.
The returned byte stream allows the response body to be consumed
without triggering JSON unmarshalling that is typically performed by the SDK.
The update document section
contains examples for both request and response byte stream cases.
The API reference contains further examples of using byte streams.
They are titled "Example request as stream" and are initially collapsed.
Expand them to see examples of:
- Byte requests:
- Bulk modify multiple documents in a database
- Byte responses:
- Query a list of all documents in a database
- Query the database document changes feed
- Cloudant Node.js SDK feature docs
- Cloudant API docs:
API reference including usage examples for Cloudant Node.js SDK API.
- TypeDoc:
Cloudant Node.js SDK API Documentation.
- Cloudant docs:
The official documentation page for Cloudant.
- Cloudant blog:
Many useful articles about how to optimize Cloudant for common problems.
You can use the SDK directly from JavaScript running in a browser if:
* Polyfills for required Node.js system modules are available.
* The server configuration allows cross-origin resource sharing (CORS).
#### Polyfills
Use either:
* A bundler that includes polyfills for Node.js system modules in the browser.
* Or a Node.js compatible browser-based runtime.
The Node.js system modules required are:
* assert
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
Additionally the SDK or its dependencies need to be able to resolve the globals:
* Buffer
*
*
* and setTimeout
Environment variables:
* NODE_DEBUG (must be resolvable from the process.env even if it is unset)
It may be possible to omit some of these requirements for specific use cases.
#### CORS
To allow CORS requests from the SDK in the browser:
1. Configure the server with a CORS origin matching the URL protocol, host and port of the JavaScript application.
2. Either
* Configure the server with a CORS headers allow list that includes the default headers plus the SDK's extra headers:
* user-agent
*
* (unless SDK request body compression is disabled)`
* Or configure the SDK to remove the extra headers from requests, for example:
js``
// Set a request interceptor to remove the headers from the requests
service.getHttpClient().interceptors.request.use(requestConfig => {
delete requestConfig.headers['User-Agent']
delete requestConfig.headers['X-IBMCloud-SDK-Analytics']
return requestConfig;
});
// Disable request body compression
service.setEnableGzipCompression(false);
If you are having difficulties using this SDK or have a question about the
IBM Cloud services, ask a question on
Stack Overflow.
If you encounter an issue with the project, you are welcome to submit a
bug report.
Before you submit a bug report, search for
similar issues and review the
KNOWN_ISSUES file to verify that your issue hasn't been reported yet.
Please consult the security policy before opening security related issues.
This SDK follows semantic versioning with respect to the definition of user facing APIs.
This means under some circumstances breaking changes may occur within a major or minor version
of the SDK related to changes in supported language platforms.
The SDK is supported on the available LTS releases of the language platform.
The LTS language versions are listed in the prerequisites:
* LTS versions currently supported by the SDK
* LTS versions for this release of the SDK
Incompatible changes from new language versions are not added to the SDK
until they are available in the minimum supported language version.
When language LTS versions move out of support the following will happen:
* Existing SDK releases will continue to run on obsolete language versions, but will no longer be supported.
* The minimum language version supported by the SDK will be updated to the next available LTS.
* New language features may be added in subsequent SDK releases that will cause breaking changes
if the new releases of the SDK are used with older, now unsupported, language levels.
Find more open source projects on the IBM GitHub page.
For more information, see CONTRIBUTING.
This SDK is released under the Apache 2.0 license. To read the full text of the license, see LICENSE.