Delete an APO attachment revision
delete
/fscmRestApi/resources/11.13.18.05/publicSectorApoAttachments/{ApoAttachmentKey}/child/ApoAttachmentAccessor/{ApoAttachmentAccessorUniqID}/child/AttachmentsRevision/{AttachmentsRevisionUniqID}
Request
Path Parameters
-
ApoAttachmentAccessorUniqID(required): string
This is the hash key of the attributes which make up the composite key for the APO Attachment Accessors resource and used to uniquely identify an instance of APO Attachment Accessors. The client should not generate the hash key value. Instead, the client should query on the APO Attachment Accessors collection resource in order to navigate to a specific instance of APO Attachment Accessors to get the hash key.
-
ApoAttachmentKey(required): integer(int64)
The unique key associated with the APO attachment.
-
AttachmentsRevisionUniqID(required): string
This is the hash key of the attributes which make up the composite key for the APO Attachment Revisions resource and used to uniquely identify an instance of APO Attachment Revisions. The client should not generate the hash key value. Instead, the client should query on the APO Attachment Revisions collection resource in order to navigate to a specific instance of APO Attachment Revisions to get the hash key.
Header Parameters
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
There's no request body for this operation.
Back to TopResponse
Default Response
No Content. This task does not return elements in the response body.