Failed to get attachment content in Forge

Thanh Le_hr3d4x

Hi everyone, I'm using this API to get attachment content on Forge: `/rest/api/3/attachment/content/{id}`.

For example:
<img src="https://api.atlassian.com/ex/jira/s213da21312312zee3/rest/api/3/attachment/content/10750" />

But it keeps returning 403.

How can I make it work, or there is any workaround for this?
Best regards,

Thanh

Peter_DevSamurai

Hi @Thanh Le , 

That 403 Forbidden on the /rest/api/3/attachment/content/{id} endpoint in Forge is usually due to missing scopes in your app's manifest.yml. And the direct img src like your example won't work because it lacks auth (Forge runs in a sandbox without direct browser access to protected APIs). 

Can you help me check if your manifest.yml is updated with read access, and then re-deploy? -> permissions: scopes: - 'read:attachment:jira' ?

This fetches binary content as a blob (avoids JSON parse errors), converts to data URL for img. If 403 persists after scope, check app logs (forge logs) for details, you might need read:jira-work too. 

IF the above direct fetch fails, try the work-around using /rest/api/3/attachment/{id} for metadata, then construct public download URL if public attachments. 

Hope the below documents are helpful for you:

• requestJira binary
• Attachment Scopes
• Display attachments

Hope everything works out well for you.

Best regards, 

Peter