List File Migration Log
List_File_Migration_LogRead-only
List file migration logs with filtering by migration ID, operation, status, type, or creation date. Supports cursor-based pagination for large result sets.
Instructions
List File Migration Logs
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Used for pagination. When a list request has more records available, cursors are provided in the response headers `X-Files-Cursor-Next` and `X-Files-Cursor-Prev`. Send one of those cursor value here to resume an existing list from the next available record. Note: many of our SDKs have iterator methods that will automatically handle cursor-based pagination. | |
| per_page | No | Number of records to show per page. (Max: 2000, 1,000 or less is recommended). | |
| filter | No | If set, return records where the specified field is equal to the supplied value. Valid fields are `file_migration_id`, `operation`, `status`, `type` or `created_at`. | |
| filter_gt | No | If set, return records where the specified field is greater than the supplied value. Valid fields are `created_at`. | |
| filter_gteq | No | If set, return records where the specified field is greater than or equal the supplied value. Valid fields are `created_at`. | |
| filter_lt | No | If set, return records where the specified field is less than the supplied value. Valid fields are `created_at`. | |
| filter_lteq | No | If set, return records where the specified field is less than or equal the supplied value. Valid fields are `created_at`. | |
| fields | No | Optional list of attribute names to include as columns in the response table. When omitted, a sensible default set is used. Useful for narrowing wide entities or surfacing fields not in the default. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |