CAP Service SDK for Node.js

Reference Documentation

We use the following conventions to describe method signatures.
Example:

cds.connect.to (service, options?) → service
cds.serve (service) … ⇢ service
↳ .from (model)
↳ .at (path)

Legend:

param? — appended question marks denote optional parameters

→ result — solid line arrows: returns the given result

⇢ result — dashed arrows: returns a [Promise] resolving to the given result

... — denotes a fluent API, eventually returning/resolving to given result

↳ — denotes subsequent methods to add options in a fluent API

The cds Facade Object: All API functions, properties and classes can be accessed through the singleton cds facade object as discussed in here.
Core Services API: This is the reference documentation for the Node.js APIs, both for design-time as well as runtime usage.
Generic Service Providers: This is the reference documentation for the Node.js APIs, both for design-time as well as runtime usage.
Messaging: This is the reference documentation for the Node.js APIs, both for design-time as well as runtime usage.
Localized Messages: Learn here how to localize generic and custom runtime errors.
Authentication: About user authentication while accessing CDS services.
Best Practices: Learn about Node.js best practices.