Project management
Jira in your product and your AI agents, through one API
The Jira toolkit covers issues, transitions, comments, projects, issue types and create fields: search with JQL, create and edit issues, move them through their workflow, comment, and look up the ids and assignable users that other calls need. The customer connects with their site credentials, and your product or AI agent calls every operation through one Connect endpoint.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/jira_create_issue/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"fields": {}
}
}How it works
From a connected customer to the first Jira call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Jira account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Jira.
Tickets from customer feedback
Create a Jira issue from a bug report or a support request in your product, using the fields that List create fields shows for the project.
Status sync with your app
Search issues by JQL, read their status and run a transition when something is done on your side, such as moving an issue to Done.
AI agent for project follow-up
Let an agent find assignable users, assign work, add comments and list the transitions available on an issue before it moves one.
Tools
13 Jira tools
- Search issuesGETSearches issues with JQL. The query must be bounded, for example project = KEY. Only the issue id comes back unless fields lists what to include. Pass the nextPageToken of the response to read the next page.
- Get issueGETReturns one issue by id or key, with all navigable fields unless fields lists what to include.
- Create issuePOSTCreates an issue. fields needs at least project, issuetype and summary, and any other field must exist on the create screen of the project, as List create fields shows. In this API version the description field takes an Atlassian Document Format object, not plain text.
- Update issuePUTEdits the fields of an issue: fields sets values, and update applies operations such as adding or removing one label. A field goes in fields or in update, never both. The status does not change here: use Transition issue. The response is empty, status 204, unless returnIssue is true.
- Delete issueDELETEDeletes an issue. An issue with subtasks is only deleted with deleteSubtasks set to true, which deletes them too. Needs the Delete issues permission in the project. The response is empty, status 204.
- List transitionsGETLists the transitions the user can make on an issue now, each with the id that Transition issue takes, its name and the status it leads to in to.
- Transition issuePOSTMoves an issue to another status by running one of its transitions. When the transition has a screen, its required fields, such as resolution, go in fields or update. The response is empty, status 204.
- List commentsGETLists the comments of an issue, with the body in Atlassian Document Format. Page with startAt and maxResults until startAt plus the returned count reaches total.
- Create commentPOSTAdds a comment to an issue, visible to everyone who can see the issue. Jira notifies the watchers by the notification scheme of the project. Returns the new comment.
- List projectsGETLists the projects the user can see, with the key and id that the issue tools and JQL take. Page with startAt and maxResults until isLast is true.
Username and password
Your customer enters the app credentials on a Connect screen, or your system sends them with POST /api/customer-toolkits, with no screen.
When connecting, your customer also enters {site}: the address of their account on the app's API.
Questions about the Jira toolkit
Do I need to build against the Jira API?
No. Connect ships 13 Jira tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Jira account?
With the mode the toolkit accepts: Username and password. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
See Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
