REST API - Get Attachment Request

/api/v1/projects/{projectid}/artifacts/{artifactid}/attachments/{attachmentid} description retrieves attachment content url structure \[blueprint uri]/api/v1/projects/{projectid}/artifacts/{artifactid}/attachments/{attachmentid} projectid the id of the project that contains the artifact with the attachment you want to retrieve artifactid the id of the artifact containing the attachment you want to retrieve attachmentid defines the id of the attachment you can obtain an attachment id by setting the attachments parameter to true in any request that retrieves artifacts (example get artifact # ) supported methods head docid\ eqnd3zptd6dwf3go3ufox get docid 7hm2r py7e84xk2msf11b http status codes 200 ok 201 successfully created 206 partial content 400 bad request this error can occur for a variety of reasons at least one uri or request body parameter is invalid, such as one of the filter docid\ sv9gjverxczcgqdn28j7u , traces, offset or limit parameters a required value has not been provided if you are submitting a post docid\ hsi lzxs8g rx ydudzkg or patch docid\ rcjvhrlby6de zgkehxui request and have not added the x http method override parameter to your request header 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 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 500 internal server error 501 not implemented examples xml example request uri https //production blueprintcloud com/api/v1/projects/220870/artifacts/220914/attachments/3194? response header {'content length' '386481', 'content disposition' 'attachment; filename=" filename=contract of carriage pdf"', 'expires' ' 1', 'server' 'blueprint', 'pragma' 'no cache', 'cache control' 'no cache', 'date' 'tue, 07 may 2013 17 02 01 gmt', 'content type' 'application/octet stream'} response body the attachment data is contained in the response body the response header contains important information about the attachment, such as content length the size of the response (that is, the attachment) filename the name of the attachment file content type the response content type, which is octet stream in this case json example request uri https //production blueprintcloud com/api/v1/projects/220870/artifacts/220914/attachments/3194? response header {'content length' '386481', 'content disposition' 'attachment; filename="contract of carriage pdf"', 'expires' ' 1', 'server' 'blueprint', 'pragma' 'no cache', 'cache control' 'no cache', 'date' 'tue, 07 may 2013 16 58 56 gmt', 'content type' 'application/octet stream'} response body the attachment data is contained in the response body the response header contains important information about the attachment, such as content length the size of the response (that is, the attachment) filename the name of the attachment file content type the response content type, which is octet stream in this case