Get Attachments
/api/v1/projects/{projectId}/artifacts/{artifactId}/attachments/{attachmentId}
Description |
Retrieves attachment content. |
URL |
[Blueprint_URI]/api/v1/projects/{ProjectId}/artifacts/{ArtifactId}/attachments/{AttachmentId}
|
Supported Methods |
HTTP status codes
-
200: OK
-
201: Successfully Created
-
206: Partial Content
-
400: Bad Request
This error can occur for a variety of reasons:
-
401: Unauthorized
- The Blueprint token is missing, invalid or expired.
-
403: Forbidden
- The applicable permissions are needed. For example, this error can occur when:
- An Author or Collaborate license is needed for access.
- Comment permissions are needed on the artifact.
- Edit permissions are needed on the change summary job.
- The applicable permissions are needed. For example, this error can occur when:
-
404: NotFound
-
Item is not found in the project. For example, this error can occur when:
- Artifact not found.
- Artifact type not found.
- Project not found.
- ALM target not found.
- Change summary job not found.
- User does not have edit permissions for this artifact, project or ALM target.
-
-
409: Conflict
- Reason for failure can be found in the response body. Additional information may also be found in the log.
-
411: Length Required
- If the Content-Length header is missing in the request.
-
413: Request Entity Too Large
- If the provided file size is larger than allowed.
-
415: Unsupported Media Type
- If the provided media type is not of MIME Multipart Content "form-data."
-
416: Request Range Not Satisfiable
- If
offset
points to a part of a collection that is not available.
- If
-
501: Not Implemented
500: Internal Server Error