Replace a folder's contents (move + reorder)
Replaces the folder's ordered contents. This is BOTH the move and the reorder call: array order becomes each segment's position, and filing a segment here pulls it out of whatever folder it was in (a segment sits in at most one folder per user), so a drag from folder A to folder B is ONE request against B. Segments previously in this folder and absent from the body are unfiled; segments the caller filed in OTHER folders and did not mention are untouched. Every id must be a segment the caller can SEE — view access is enough, since organising your own rail is not editing the segment. Unknown and invisible ids are reported together in one 400 (error.details.errors.segmentIds) so the response cannot be used to discover whether a private segment exists; nothing is moved.
Request
- Base URLhttp://localhost:3009
- AuthHTTP bearer
Path parameters
Request body
Response
The folder's contents after the write.
Example response
{
"data": {
"items": [
{
"segmentId": "01J9Z8Q3K2X7M4N5P6R7S8T9V0"
}
]
}
}Changes
No recorded changes to this operation across all 1 revision of this API.