routes folder at installation.
Below we’ve detailed what the next() statement does. Those snippets can be used when overriding those routes, as explained here.
Create a record
Update a record
Note that the update of
belongsTo fields is managed by another route.Delete a record
Get a list of records
Get a number of records
Get a record
Export a list of records
Delete a list of records
Other available routes
Some other routes exist but are not generated automatically because it’s less likely that you’ll need to extend or override them. Here is the list:Relationship routes
GET /forest///relationships/⟶ List has many relationships GET /forest///relationships//count
⟶ Count has many relationships PUT /forest///relationships/
⟶ Update a belongs to field POST /forest///relationships/
⟶ Add existing records to has many relationship GET /forest///relationships/.csv
⟶ Export all has many relationships PUT /forest///relationships//
⟶ Update an embedded document (inside a list) DELETE /forest///relationships/
⟶ Dissociate records from relations
Action routes
POST /forest/actions//values⟶ Get the default values for this action