<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=533968) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal When [exporting a project](https://docs.gitlab.com/api/project_import_export/#export-status), after export is scheduled, the client is expected to poll for status until export is ready to be downloaded. When the export is completed, it would be make things easier for a client to include a checksum of the project export content at the status endpoint. After a client has downloaded the data, it can better verify the content is not corrupt. #### Suggested solution When a project export is finished, the API already returns additional fields under `_links`. The suggested solution is when `export_status="finished"`, the field `crc32c: uint32` is added to root of response object, with the CRC32C calculated checksum. This algorithm is suggested due to being fast and collision is not critical, as the purpose is error detection. <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->