'rest' capability for WebSocket Token API
Contents
Overview
Provides an interface for CRUD operations on entities of static and dynamic classes.
To work, the integration_point (webservice) entity whose token is used for the connection must have a role with access to the route /ws#rest with the WEBSOCKET method.
It also requires binding to a user who has role permission for the requested operation on the collection endpoint in the REST API.
Every non-empty change results in notifications being generated to subscribers.
-
Request construction is similar to WebSocket User API.
-
Connection setup with the
setup_restrequest (theskip_response_entityoption) is similar to WebSocket User API.