Rediger

Database views in the REST API

Views are supported as alternatives to tables in Data API builder (DAB). A view can be exposed through REST endpoints with minimal configuration.

Configuration

To expose a view:

  • Set source.type to "view"
  • Set source.object to the fully qualified view name
  • To identify a row uniquely, define key-fields
  • Grant permission using the "read" action (and optionally "create", "update", "delete" if the view is updatable)

CLI example

dab add BookDetail \
  --source dbo.vw_books_details \
  --source.type "view" \
  --fields.name "id" \
  --fields.primary-key "true" \
  --permissions "anonymous:read"

Configuration example

"BookDetail": {
  "source": {
    "type": "view",
    "object": "dbo.vw_books_details",
    "key-fields": [ "id" ]
  },
  "permissions": [
    {
      "role": "anonymous",
      "actions": [ "read" ]
    }
  ]
}

REST behavior

  • Supports all REST verbs: GET, POST, PUT, PATCH, DELETE
  • Default behavior is identical to table-backed entities
  • Operations succeed only if the view is updatable and appropriate permissions are set

Example request

GET /api/BookDetail/id/42

Returns the row from vw_books_details with id = 42.

Permissions

  • Use the read action for readonly views
  • Use create, update, and delete only if the view is updatable

Limitations

  • key-fields are required
  • Views don't support relationships
  • Pagination, filtering, and sorting are supported if the view behaves like a table

Related content

  • Last updated on