Hi @david.gunter - yes. We need to add your app to an internal whitelist. Otherwise the API will not work.
Can you point me/us to the documentation for that API?
This is fine for ID to email address. What about the other way around? Say you have been given an email address - how would you query Jira to get an account ID for that address (if one exists)?
How, in the context of GDPR and the Email API, the following REST endpoint works: https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-issue-issueIdOrKey-notify-post
- Does it still work? Can we still use it?
- It used to accept usernames (at least example suggests it). Has it been changed to accept Atlassian account ID?
It is either not GDPR ready or documentation was not updated.
Another question: are there any plans to let apps post notifications to the new Jira notification area? Is there any issue that we can watch and vote? I wasn’t able to find any. Our customers ask for that.
Is access to the Email API available restricted to Apps, or could requests outside an App also be given access? Also, is there public documentation on the whitelisting mechanism?
@MichaelNelson - The restricted email API is only available to apps. Direct REST calls or functionality provided through scripts, etc. using API tokens are not. The whitelisting mechanism is and will not be documented. The process for getting whitelisted is covered above and also available here: https://developer.atlassian.com/cloud/jira/platform/profile-visibility/
Thank you for clarifying this, Alexandra.
@akassab I have a request open since 25th of July, could someone finally take a look - https://ecosystem.atlassian.net/servicedesk/customer/portal/14/DEVHELP-3190
Thank you for the guidelines. Could somebody explain me, can I request access to the Email API for a simple 3LO app created via https://developer.atlassian.com/apps/create if the app itself is private and still is in “In development” status?
@DmitryBogomolov no 3LO apps can’t have access to the email API. Access requires at Atlassian Connect app key. 3LO apps should not need it as they will receive non-public PD for the users who grant access.
I’m guessing that this also means that existing customers will have to manually approve the upgrade to newer versions (with extended scope) in “Manage apps” tab?
I raised a Request access to the Email API ticket in DEVHELP a week ago. There’s been no follow-up from Atlassian yet. I think my ticket might have been lost due to refactoring DEVHELP. Could you suggest who to contact to check that?
How quickly can I expect my ticket to be reviewed?
It has been a few days now with no updates.
@akassab Might be worthwhile to reference this info in the documentation here: https://developer.atlassian.com/cloud/jira/platform/rest/v3/?utm_source=%2Fcloud%2Fjira%2Fplatform%2Frest%2F&utm_medium=302#api-rest-api-3-user-get
@akassab How long it usually takes for the app from being approved to being included in whitelist so API can be used? I got my application approved month ago (24th of March), but still I cannot use the API
@akassab, same here, waiting for over a month and nothing.
We are a data integration platform that one of our clients requested access to the Email API.
After getting his access, will we be able to use his access to let him pull his data? Do we need to also request for access?
@TsilaHadad - Access is granted at the app level (where app is defined as a unique connect app key). You shouldn’t need separate apps for the same use case.
@akassab, thanks a lot for your answer.