deleteFavoritesFromBody
BooleanWrapper deleteFavoritesFromBody(BaseBatchRequestDto)
DELETE /api/2.0/files/favorites
Delete favorite files and folders
Removes the favorite mark from the listed files and folders for the calling account. Nothing is deleted from storage: the entries keep their place, their content and their sharing, and only disappear from GET api/2.0/files/@favorites; to delete the entries themselves call PUT api/2.0/files/fileops/delete instead. Marks of other members are untouched, and read access to each item is enough to call it. The ids go into the JSON body documented here; the same route also accepts them as repeated fileIds and folderIds query parameters, but only in a request that carries no JSON body at all. Numeric ids address entries stored in the portal itself, string ids entries on a connected third-party account. The answer is true whenever the request was understood, which an empty request, an id that does not exist and an item that was never marked all achieve, so it does not report how many marks were dropped. returnSingleOperation arrives with the shared body and does nothing here. Repeating the call is safe. Use POST api/2.0/files/favorites to mark entries again.
Parameters
| Name | In | Type | Description | Notes |
|---|---|---|---|---|
| BaseBatchRequestDto | body | BaseBatchRequestDto | [optional] |
Responses
| Status code | Description | Type | Response headers |
|---|---|---|---|
| 200 | Always true: the marks named in the request are gone or were never there | BooleanWrapper | X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset |
| 400 | The request body cannot be read, or a third-party identifier refers to a storage account that is not connected | - | - |
| 404 | A third-party identifier names a storage type the portal does not know | - | - |
| 500 | An id is a number that is not a 32-bit integer, or a third-party identifier carries a storage account number beyond the 32-bit range | - | - |
| 401 | Unauthorized | ErrorApiResponse | - |
| 429 | Too Many Requests. | ErrorApiResponse | Retry-After |
| 502 | Bad Gateway. Returned by the reverse proxy, response body may be HTML and not JSON. | - | - |
| 503 | Service Unavailable. Returned by the reverse proxy, response body may be HTML and not JSON. | - | - |
Return type
Authorization
Basic, OAuth2 (scopes: read, write), ApiKeyBearer, asc_auth_key, Bearer, OpenId
HTTP request headers
- Content-Type: application/json
- Accept: application/json