JSM Asset GET Schema and Mapping 500 Internal Server Error

Hi everyone,

I’ve developed an External Importer App following the Atlassian Assets Cloud documentation: Introduction

I implemented everything as described — using the container token, schema, and mapping setup — and it worked fine before.
However, now I can’t fetch the schema via API anymore.

I’m calling this endpoint: https://api.atlassian.com/ex/jira/{cloudId}/jsm/assets/workspace/{workspaceId}/v1/importsource/{importSourceId}/schema-and-mapping

All variables (cloudId, workspaceId, importSourceId) are correct, the manifest is properly configured, and the required scope (import:import-configuration:cmdb) is set.

It used to work when the endpoint was: https://api.atlassian.com/jsm/assets/workspace/${workspaceId}/v1/importsource/${importSourceId}/schema-and-mapping

Now:

The old endpoint returns 500 Internal Server Error

The new endpoint returns 401 Unauthorized

I couldn’t find any note about this change in the changelog or docs.

My request is look like

const currentMapping = await fetch(url, {
method: ‘GET’,
headers: {
Authorization: Bearer ${token}
}
});

I also tried Basic Auth with a base64 token — same result.
Has anyone else experienced this issue, or found a fix/workaround?

Thanks in advance!

1 Like

Bump - this is breaking a bunch of our products currently.