Trying to call the https://<itsite>api.atlassian.com/jsm/assets/workspace/ endpoint but getting "errorMessage": "Site temporarily unavailable", "errorCode": "OTHER"

JSM Development JSM Cloud
, ,
1

jsm
jsm1233×532 9.72 KB

I followed this documentation, but can’t seem to get it working. I set my authorization to basic auth and set my email as my username, then api key as the password. Also tried the Bearer Token in postman and can’t get anything to work. Any Ideas?

2

Hello @JakeBurnette

In that guide, at Step 2, it asks you to get your workspace ID. Did that endpoint return your workspace ID?

Are you then able then use that workspace ID to make a basic request to, say, the v1 Get objectschema List endpoint:
GET https://api.atlassian.com/jsm/assets/workspace/{workspaceId}/v1/objectschema/list

4

hello,
I do get a return on the workspace ID, but when I run the https://api.atlassian.com/jsm/assets/workspace/{workspaceId}/v1/objectschema/list
I get a 401 unauthorized.

5

So, this indicates there are two possibilities:

  1. You do not have the permissions to access that resource
  2. You have permission to access that resource, but you’ve encoded or supplied your credentials incorrectly in the request

You’ll need to supply samples of your code that shows HOW you are encoding your credentials and then bundling them into the request. I also recommend that you use Postman to test the same request outside your code. Use Basic auth with your username (email address) and password (API Token) for credentials, exactly as you would for JSM API endpoints or Jira API endpoints

In the interim, you can test if you actually have permissions to access that resource by using your web browser and:

  1. Login to your Atlassian account and go to your organisation’s JSM instance
  2. Open a new tab in your web browser and paste in the request URL, then hit enter
  3. Since you are already authenticated, if you have permission to access that resource, the endpoint will respond correctly
  4. If you don’t have permission, you’ll get the 401 error, so it will then be up to you to liaise with your organisation’s IT department to be given the required permission
1 Like
6

Thank you!