Is there a external facing customer API?

[Elijah Penney]

My company is looking to move to Cloud Jira and we'd like to be able to utilize the the v2 / v3 API to allow our Customers (added into Cloud Jira as Customers) to pull ticket information associated with their organization.

The documentation talks about needing an API token in order to authenticate with Basic Auth, but there doesn't seem to be any way to get this type of token as a Customer instead of a full Jira user.

Is there any documentation on this?

[Brant Schroeder]

@Elijah Penney Welcome to the Atlassian community.

In order to use the API you need a Jira License.  You could submit a feature request here https://jira.atlassian.com/secure/Dashboard.jspa 

[Elijah Penney]

@Brant Schroeder Thanks for getting an answer posted so quickly!

A small follow-up to this, if we were to give out seats in our Cloud Jira to customers, is there a way to restrict a Jira User (not a Customer) to only seeing a specific Organization's content? 

Having access to that API is a pretty important request we're getting from a lot of potential clients and have been unable to find a sustainable solution for, so even if it does require paying for an extra user, or multiple, it would be worth whatever setup or price we would need for them.

[Brant Schroeder]

You would not be able to filter by the organization as this is a portal restriction but has no bearing on a Jira user or agent.  You could setup issue security that would apply security on the issue based on the organization when the issue is created in the workflow.  This would require JSU or scriptrunner so you could have some logic to apply the issue security.  You could then give the user access only to that issue security. 

My question is what is the customer after.  They will be able to see all the organization's ticket information in the portal if they log in.  Seems like you are just recreating something that already exsists.