Important: All Cloudant documentation has moved to the IBM Bluemix platform. You can find the new content here, and the CORS topic in particular here.

Content on this page will no longer be updated (Jan 31st, 2017).

Cross-origin resource sharing (CORS) is a mechanism that allows resources such as JSON documents in a Cloudant database to be requested from Javascript running on a website loaded from another domain. These “cross-domain” requests would normally be forbidden by web browsers, due to the same origin security policy.

CORS defines a way in which the browser and the server interact to determine whether or not to allow the request. For Cloudant, there are two use cases in which CORS might be a good solution.

  1. You have a website on and you want scripts on this website to be able to access data from To do this, add to your list of allowed origins. The effect is that scripts loaded from this domain are then allowed to make AJAX requests to your Cloudant databases. By using HTTP auth with CORS requests, users of your application are able to access their database only.
  2. You want to allow third parties access to your database. An example might be where you have a database that contains product information, and you want to give sales partners access to the information from Javascript running on their own domain. To do this, add their domain to your list of allowed origins. The effect is that scripts running on their website are able to access your Cloudant database.

Browser support

CORS is supported by all current versions of commonly used browsers.


Storing sensitive data in databases that can be accessed using CORS is a potential security risk. When you place a domain in the list of allowed origins, you are trusting any of the Javascript from the domain. If the web application running on the domain is running malicious code or has security vulnerabilities, sensitive data in your database might be exposed.

In addition, allowing scripts to be loaded using HTTP rather than HTTPS, and then accessing data using CORS, introduces the risk that a man in the middle attack might modify the scripts.

To reduce the risk:

Configuration endpoints

Method Path Description
GET /_api/v2/user/config/cors Returns the current CORS configuration
PUT /_api/v2/user/config/cors Changes the CORS configuration

JSON format

Setting the CORS configuration

PUT /_api/v2/user/config/cors HTTP/1.1
Host: $
Content-Type: application/json
curl https://$USERNAME:$PASSWORD@$ -H 'Content-Type: application/json' -X PUT -T cors.json
# where cors.json is a file with the following JSON document:
    "enable_cors": true,
    "allow_credentials": true,
    "origins": [

PUTting a json document with the example structure to /_api/v2/user/config/cors sets the CORS configuration. The configuration applies to all databases and all account level endpoints in your account.

{ "ok": true }

The response tells you whether the configuration has been updated successfully.

Reading the CORS configuration

GET /_api/v2/user/config/cors HTTP/1.1
curl https://$USERNAME:$PASSWORD@$

GETting /_api/v2/user/config/cors

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 178
    "enable_cors": true,
    "allow_credentials": true,
    "origins": [

… returns the CORS config in a JSON document.


CORS support is available in the Cloudant dashboard.

You can update your CORS settings using the CORS tab within the dashboard:

CORS dashboard illustration

To see the current CORS configuration, simply open the CORS tab in the dashboard.

You can enable or disable CORS using the “Enable CORS” checkbox. This corresponds to the enable_cors option when changing the CORS configuration from within an application.

To specify that CORS is enabled for all domains, select the “All domains (*)” option.

To specify that CORS is enabled only for exact origin domains, list each of the domains or subdomains using the “Restrict to specific domains” option. For each domain, provide a full URL, preferably using the https prefix for additional security.