backup automation via REST API

[Maik Foerster]

For some reason I have difficulties to get a valid response when running the curl script

This:

curl --location 'https://api.atlassian.com/public/backup-management/v2/orgs/the-new-created-token/policies' \
--header 'X-Atl-Account-Id: IDIDID \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '{
"product": "JIRA",
"includeAttachments": true,
"includePersonalSpaces": true,
"scheduleRequest": {
   "interval": "ONCE",
   "startDate": "today and now"
},
"policyName": "jira"
}'

leads to that:

{
   "timestamp": "2026-02-04T15:49:45.424+00:00",
   "status": 404,
   "requestId": "161bca59-59861",
   "message": null
}

My brain is unable to realize why it leads to ERR 404

Is there anyone with similar experience and know how to solve it or where is the point I'm thinking wrong?

[Trudy Claspill]

Hello @Maik Foerster 

Welcome to the Atlassian community.

You said you included "the newly created token" in the API Endpoint call:

 'https://api.atlassian.com/public/backup-management/v2/orgs/the-new-created-token/policies' \

What you need to have in that position is the ID of your Atlassian Cloud Organization. This document provides guidance on how to get the Organization ID.

https://confluence.atlassian.com/cloudkb/retrieve-my-atlassian-cloud-organization-s-id-1207189876.html

Additionally as per the documentation at 

https://developer.atlassian.com/cloud/backup-management-apis/guides/authorization/

...if you are going to use the Authorization header it needs to be in this syntax:

 --header "Authorization: Basic <BASE64_ENCODED_STRING>"

Did you include Basic in your Authorization data?

Did you base64 encode your email and token?

[Maik Foerster]

Thanks a lot - will test tomorrow, when back in office. thanks again

[Maik Foerster]

sorry, it was not the point. 
But now I am fom 404 to 401  - 

{"code":401,"message":"Unauthorized"}%

Seems the right way, just the authorization fails for some reason

[Trudy Claspill]

Have you changed the headers or payload? If so, show us what you are using now.

If you did not change anything then see in my original reply what I said about the Authorization header.