The Standard Assets REST API Guide will walk you through a workflow that is designed for users that want to use the REST API to complete tasks other than importing data or data structures into Assets. It follows the normal procedure of making REST API calls using basic auth.
This workflow includes the following steps:
Authentication: For authenticating directly against the REST API, the Assets in Jira Service Management REST API supports basic auth ( see Basic auth for REST APIs).
Authorization: For making calls directly against the REST API, authorization is based on the user used in the authentication process.
See Security overview for more details on authentication and authorization.
Please note that import APIs might support extra means of authentication, such as OAuth tokens. Read more about this in the Imports REST API guide.
If you are using the Imports REST API, only container tokens will be accepted, unless you're building on Atlassian Forge. For more information on how to integrate with Assets using Forge, see: Importing Third Party data into Assets using Forge.
Workspace ID: The Jira Service Management REST API uses the to identify your individual instance of Assets. You must include the when making any calls to the REST API.
You can discover your through the following endpoint:
https://<JSM Premium Site Name>.atlassian.net/rest/servicedeskapi/assets/workspace
The workspaceId should be included in any requests as follows:
Rate this page: