Abort an Upload

Hard-delete a file row whose S3 PUT failed.

Refuses with 409 if the file is already confirmed — confirmed files must use the regular soft-delete endpoint.

DELETE /files/{file_id}/abort-upload

Abort Upload

cURL

curl --request DELETE \
  --url https://api.example.com/files/{file_id}/abort-upload \
  --header 'Authorization: Bearer <token>'

200

{}

Hard-deletes a file row whose PUT to S3 never happened or failed. This is the only hard delete in the Files API — every other delete is the soft delete described in Delete a File. Only works while the file is still status: "pending"; a confirmed upload must go through that regular soft-delete instead.

Auth

Requires a CRM manage scope and an active organization on the token. Any *:manage scope qualifies — in practice contacts:manage, deals:manage, companies:manage, or activities:manage.

Response

Field	Type	Description
aborted	boolean	Always true on success.

Errors

Status	Cause
404 Not Found	File doesn’t exist in this org.
409 Conflict	The file is already status: "uploaded" — use Delete a File instead.

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

file_id · string · required

UUID of the pending (unconfirmed) file upload to abort.

Response

200

application/json

Successful Response

{key} · boolean