跳到主要内容

getFolderHistory

HistoryArrayWrapper getFolderHistory(folderId, fromDate, toDate, count, startIndex)

GET /api/2.0/files/folder/{folderId}/log

Get folder history

Lists what has happened to a folder and to the entries inside it - creations, renames, uploads, moves, deletions and changes of access - each record naming the action, the moment it happened and the member behind it. Records that belong to one action are grouped, so a batch arrives as a single entry carrying the rest of itself in related, and the list runs from the most recent record backwards. fromDate and toDate narrow the period, startIndex and count page through the result, and the number of records matching the request is reported in the response headers rather than in the body. Any member who can read the folder may read its history; a caller without access is answered with 403 and a folder that does not exist with 404. When the folder is a form-filling folder the caller reached through a filling invitation, the history is narrowed to what that caller may see. The call is read-only. To take the same history away as a spreadsheet, start a report with POST api/2.0/files/folder/{folderId}/log/report.

Parameters​

NameInTypeDescriptionNotes
folderIdpathInteger (int32)The folder whose activity log is read; the log covers the folder itself and the entries inside it.[required] [example: 1]
fromDatequeryDate (date-time)The earliest moment an entry may have, read in the time zone of the portal; left out, the log starts at the oldest entry the portal still keeps.[optional] [example: 2025-01-01T00:00:00.0000000Z]
toDatequeryDate (date-time)The latest moment an entry may have, read in the time zone of the portal; left out, the log ends at the newest entry.[optional] [example: 2025-12-31T23:59:59.0000000Z]
countqueryInteger (int32)How many entries one page holds. The number of entries that match the query is reported in the response headers, not in the body.[optional] [example: 25] [min: 1] [max: 100]
startIndexqueryInteger (int32)How many entries to skip before the page begins, counted from the newest one, so pages are taken by adding the page size to it.[optional] [example: 0]

Responses​

Status codeDescriptionTypeResponse headers
200One page of the folder history, the most recent record firstHistoryArrayWrapperX-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
400A parameter has the wrong type, the count is outside its allowed range, or fromDate or toDate is not a date and time ending in Z or a UTC offset--
403The caller may not read this folder--
404The folder does not exist--
401UnauthorizedErrorApiResponse-
429Too Many Requests.ErrorApiResponseRetry-After
500Internal Server Error.ErrorApiResponse-
502Bad Gateway. Returned by the reverse proxy, response body may be HTML and not JSON.--
503Service Unavailable. Returned by the reverse proxy, response body may be HTML and not JSON.--

Return type​

HistoryArrayWrapper

Authorization​

Basic, OAuth2 (scopes: read, write), ApiKeyBearer, asc_auth_key, Bearer, OpenId

HTTP request headers​

  • Content-Type: Not defined
  • Accept: application/json