How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Jira Issue attachments API

This resource represents issue attachments and the attachment settings for Jira. Use it to get the metadata for an attachment, delete an attachment, and view the metadata for the contents of an attachment. Also, use it to get the attachment settings for Jira.

Jira Issue attachments API is one of 132 APIs that Jira publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Issue Attachments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and an API reference.

This API exposes 8 operations across 7 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df.

Requests are made against a single base URL, https://your-domain.atlassian.net.

8 operations 7 paths 18 schemas 1 DELETE6 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df
Base URL
https://your-domain.atlassian.net/rest/api/2
Authentication
OAuth 2.0, HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Jira Issue attachments API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 186 scopes. It accepts HTTP basic authentication (basicAuth).

  • OAuth2 — OAuth2 scopes for Jira
  • basicAuth — You can access this resource via basic auth.

Paths & Operations 8

Across 7 paths, the API surfaces 8 operations — 1 DELETE, 6 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Issue Attachments 8

This resource represents issue attachments and the attachment settings for Jira. Use it to get the metadata for an attachment, delete an attachment, and view the metadata for the…

GET
/rest/api/3/attachment/content/{id}
Get attachment content
getAttachmentContent 2 params → 200206303400401403404416
GET
/rest/api/3/attachment/meta
Get Jira attachment settings
getAttachmentMeta → 200401
GET
/rest/api/3/attachment/thumbnail/{id}
Get attachment thumbnail
getAttachmentThumbnail 5 params → 200303400401403404
DELETE
/rest/api/3/attachment/{id}
Delete attachment
removeAttachment 1 param → 204403404
GET
/rest/api/3/attachment/{id}
Get attachment metadata
getAttachment 1 param → 200401403404
GET
/rest/api/3/attachment/{id}/expand/human
Get all metadata for an expanded attachment
expandAttachmentForHumans 1 param → 200401403404409
GET
/rest/api/3/attachment/{id}/expand/raw
Get contents metadata for an expanded attachment
expandAttachmentForMachines 1 param → 200401403404409
POST
/rest/api/3/issue/{issueIdOrKey}/attachments
Add attachment
addAttachment 1 param body → 200403404413

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are User (16 properties), ApplicationRole (14 properties), UserDetails (10 properties), AttachmentMetadata (10 properties). Each schema is shown below with its type and property counts.

AttachmentArchiveItemReadable
object
Metadata for an item in an attachment archive.
5 properties
AvatarUrlsBean
object
4 properties
User
object
A user with details as permitted by the user's Atlassian Account privacy settings. However, be aware of these exceptions: User record deleted from Atlassian: T…
16 properties
Attachment
object
Details about an attachment.
9 properties
GroupName
object
Details about a group.
3 properties
Resource
object
9 properties
ListWrapperCallbackGroupName
object
AttachmentArchiveMetadataReadable
object
Metadata for an archive (for example a zip) and its contents.
5 properties
ApplicationRole
object
Details of an application role.
14 properties
UserDetails
object
User details permitted by the user's Atlassian Account privacy settings. However, be aware of these exceptions: User record deleted from Atlassian: This occurs…
10 properties
AttachmentSettings
object
Details of the instance's attachment settings.
2 properties
ListWrapperCallbackApplicationRole
object
MultipartFile
object
8 properties
SimpleListWrapperGroupName
object
5 properties
AttachmentMetadata
object
Metadata for an issue attachment.
10 properties
AttachmentArchiveImpl
object
2 properties
SimpleListWrapperApplicationRole
object
5 properties
AttachmentArchiveEntry
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jira-issue-attachments-api-openapi.yml Raw ↑

Other APIs Jira publishes across the network.

Jira Cloud Platform REST API v2
Jira Service Management Operations REST API
Jira Align REST API
Jira Customer Service Management REST API
Jira Issue Comments API
Jira Issue Priorities API
Jira Issue Search API
Jira Issue Statuses API
Jira Issue Transitions API
Jira Issue Types API
Jira Issues API
Jira Projects API
Where this information came from

This is an independent, third-party profile of Jira Issue attachments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.