Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Manual Automation Rules via REST API – Invalid ARI Format?

Lukas Flaig
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 11, 2025

Hello,

 

I’m working for a client who wants to access manual automation rules for an issue from their own server using the Atlassian Automation REST API (see the documentation).

 

According to the docs, the endpoint to use is POST Search for manual rules. I’m trying to query manual rules for an issue using its internal numeric ID. I construct the ARI as follows:

"ari:cloud:jira:issue/12345"   <-- Dummy ID (12345) for illustration

 

Below is the relevant code snippet:

Screenshot 2025-01-11 at 17.42.00.png

 

However, I keep receiving the following error:

{

    "errors": [

        {

            "code": "api.validation.invalid-ari",

            "field": "objects[0]",

            "id": "8ffe1e67-7eb9-43cd-ad99-3b8979ff85a2",

            "status": 400,

            "title": "'ari:cloud:jira:issue/12345' is not a valid ARI"

        }

    ]

}

 

I’m certain that I’m using the correct internal numeric ID (and not the visible issue key). However, I can’t find any additional guidance in the documentation regarding the proper ARI format.

 

Am I missing something or are there additional requirements for querying manual automation rules?

 

Any help is appreciated!

 

Thanks in advance!

1 answer

1 accepted

4 votes
Answer accepted
Sahir Maharaj
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 11, 2025

Hello @Lukas Flaig

Based on my understanding, the error with the ARI format might stem from the structure or scope of the ARI being used. The ARI for manual automation rules typically requires a fully qualified identifier, which includes the site ID, project ID, and issue details in the proper format.

For example, ARIs often follow the format: ari:cloud:jira:<resource>/<resource-ID> with clear mapping to your site and project.

I’d suggest re-checking the exact structure of your ARI in relation to the documentation and ensuring it matches the expected pattern.

Lukas Flaig
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 12, 2025

Thank you very much for your helpful input. Unfortunately, I couldn’t find any information about ARI in the official documentation. However, I discovered the correct working format on the Atlassian Developer site, which is "ari:cloud:jira:{siteId}:issue/{issueId}".

 

Thanks again for your support!

Like Sahir Maharaj likes this

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, confluence, loom, atlassian intelligence, ai notes, ai-powered meeting notes, atlassian community events, ace, confluence ai, loom ai integration, ai note-taking, atlassian ai features, team '25, atlassian live learning, confluence automation

Unlock AI-powered meeting notes: Join our live learning session! 📹

Did you catch the news at Team ‘25? With Loom, Confluence, Atlassian Intelligence, & even Jira 👀, you won’t have to worry about taking meeting notes again… unless you want to. Join us to explore the beta & discover a new way to boost meeting productivity.

Register today!
AUG Leaders

Atlassian Community Events