Table of Contents
GET /db/_design/design-doc
PUT /db/_design/design-doc
DELETE /db/_design/design-doc
COPY /db/_design/design-doc
GET /db/_design/design-doc/attachment
PUT /db/_design/design-doc/attachment
DELETE /db/_design/design-doc/attachment
GET /db/_design/design-doc/_info
GET /db/_design/design-doc/_view/view-name
POST /db/_design/design-doc/_view/view-name
POST /db/_design/design-doc/_show/show-name
POST /db/_design/design-doc/_show/show-name/doc
GET
/db/_design/design-doc/_list/list-name/other-design-doc/view-name
POST
/db/_design/design-doc/_list/list-name/other-design-doc/view-name
GET /db/_design/design-doc/_list/list-name/view-name
POST /db/_design/design-doc/_list/list-name/view-name
PUT /db/_design/design-doc/_update/updatename/doc
POST /db/_design/design-doc/_update/updatename
ALL
/db/_design/design-doc/_rewrite/rewrite-name/anything
In CouchDB, design documents provide the main interface for building a CouchDB application. The design document defines the views used to extract information from CouchDB through one or more views. Design documents are created within your CouchDB instance in the same way as you create database documents, but the content and definition of the documents is different. Design Documents are named using an ID defined with the design document URL path, and this URL can then be used to access the database contents.
Views and lists operate together to provide automated (and formatted) output from your database.
A list of the available methods and URL paths are provided below:
Table 8.1. Design Document API Calls