> ## Documentation Index > Fetch the complete documentation index at: https://docs.landfall.ai/llms.txt > Use this file to discover all available pages before exploring further. # Recover a pending upload - what landed, with ETags, and URLs for what did not > The recovery path, for a client that lost its part manifest or its place. This is the only endpoint that asks S3 what it actually stored, so it is deliberately off the happy path: a normal upload never calls it, and a LIST request per upload is negligible. It returns the ETag of every part S3 holds - which is what makes a lost manifest recoverable, since `finish` otherwise depends entirely on ETags the client captured - plus a fresh upload URL for every part still missing. Also extends the upload's deadline. ## OpenAPI ````yaml /api-reference/openapi.yml get /data-assets/{username}/{namespace}/{assetId}/versions/{versionNo}/status openapi: 3.0.3 info: title: DataLinks version: 3.10.0 servers: - url: https://api.datalinks.com/api/v1 description: production server security: - bearerAuth: [] - openId: - implicit paths: /data-assets/{username}/{namespace}/{assetId}/versions/{versionNo}/status: get: tags: - data-assets summary: >- Recover a pending upload - what landed, with ETags, and URLs for what did not description: > The recovery path, for a client that lost its part manifest or its place. This is the only endpoint that asks S3 what it actually stored, so it is deliberately off the happy path: a normal upload never calls it, and a LIST request per upload is negligible. It returns the ETag of every part S3 holds - which is what makes a lost manifest recoverable, since `finish` otherwise depends entirely on ETags the client captured - plus a fresh upload URL for every part still missing. Also extends the upload's deadline. operationId: getDataAssetUploadStatus parameters: - name: username in: path description: The username associated with the request. required: true schema: type: string - name: namespace in: path description: Namespace for the dataset. required: true schema: type: string example: cinematography - name: assetId in: path description: The data asset's id. required: true schema: type: string format: uuid - name: versionNo in: path description: The version number. required: true schema: type: integer responses: '200': description: Current state of the pending upload content: application/json: schema: $ref: '#/components/schemas/DataAssetUploadStatusResponse' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '422': $ref: '#/components/responses/UnprocessableEntity' components: schemas: DataAssetUploadStatusResponse: required: - assetId - expiresAt - missing - partSize - totalParts - uploadId - uploaded - versionNo type: object properties: assetId: type: string format: uuid versionNo: type: integer uploadId: type: string partSize: type: integer format: int64 totalParts: type: integer expiresAt: type: string format: date-time uploaded: type: array description: > Every part S3 currently holds, with the ETag it stored. These are valid finish inputs - a client that lost its manifest can rebuild it from here rather than re-uploading. items: $ref: '#/components/schemas/FinishPartInput' missing: type: array description: >- Fresh upload URLs for the parts not yet stored. Empty means ready to finish. items: $ref: '#/components/schemas/PresignedUploadPart' FinishPartInput: required: - etag - partNumber type: object properties: partNumber: type: integer description: The 1-based part number, exactly as issued in a `next[]` entry. etag: type: string description: > WHERE THIS COMES FROM: the value of the `ETag` response header of the `PUT` that uploaded this part. There is no other source - the API never sees the part bytes and does not ask S3 what it stored, so a client that loses an ETag cannot finish the version and must abort and re-upload it. Capture it from each part `PUT` response and keep it until `finish`. Quotes may be included or stripped; both are accepted. For browser clients the bucket CORS must send `Access-Control-Expose-Headers: ETag`, or the header is unreadable from script and the ETag is silently lost. S3 validates every (partNumber, etag) pair when the upload is completed: a wrong ETag, or one for a part that was never uploaded, fails the whole `finish` with 422 and commits nothing. A forged ETag therefore cannot corrupt an asset. example: d41d8cd98f00b204e9800998ecf8427e description: >- One uploaded part, identified by its number and the ETag S3 returned for it. PresignedUploadPart: required: - partNumber - size - url type: object properties: partNumber: type: integer url: type: string size: type: integer format: int64 ErrorResponse: required: - error_code - message type: object properties: error_code: type: string example: UNAUTHORIZED error_message: type: string example: '' message: type: string example: Missing authentication token sub_errors: type: array items: required: - code - message type: object properties: code: type: string message: type: string responses: Unauthorized: description: >- Unauthorized. This error occurs if the authentication token is missing or invalid. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' Forbidden: description: Forbidden. The user does not have access to this resource. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' NotFound: description: The requested resource was not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' UnprocessableEntity: description: Invalid request (e.g. version out of retention, TTL above max). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: bearerAuth: type: http description: > Use a Bearer token for authentication. Submit the token using the `Authorization` header: `Authorization: Bearer `. scheme: bearer openId: type: oauth2 flows: implicit: authorizationUrl: >- https://login.datalinks.com/realms/datalinks-realm/protocol/openid-connect/auth scopes: openid: openid ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.