Delete one project file
Deletes one project file through the unified project API.
Features:
- For Advanced Replication, deletion behavior depends on the file's current phase: a draft file (never committed) is removed immediately and permanently. An approved file (already part of a committed revision) is not removed immediately — instead it is marked pending_deletion, a tombstone that keeps the file visible in historical/committed revisions until the next commit finalizes the removal, preserving lineage for already-shipped content. Deleting a file that is already pending_deletion is a no-op (idempotent).
- For Mainframe Replication, the file is removed immediately; there is no draft/approved phase distinction.
- Removes the file from the project's current working set.
Use Cases:
- VS Code extension deletes a file from the project explorer.
- User cleans up unused files from a project.
Authorization: Requires replication-pipeline::delete when permission harmonization is enabled; otherwise, replication-pipeline::manage.
Request
- Base URL: https://integration-adapter.connect.cloud.precisely.com
- URL: https://integration-adapter.connect.cloud.precisely.com/v1/integration/projects/{projectId}/files/{fileId}
- Auth: HTTP bearer
Path parameters
Unique identifier of the project
Unique identifier of the file to delete
Query parameters
Supported project types for unified project operations
Project type (required for routing): REPLICATION | MAINFRAME_REPLICATION | ADVANCED_REPLICATION
Unique identifier of the Mainframe Replication pipeline (Mainframe Replication only). Ignored for Advanced Replication.
Optional revision number targeted by the delete
Headers
Optional If-Match header value for optimistic concurrency control
Response
Project file deleted
Changes
No recorded changes to this operation across all 1 revision of this API.