# Axosoft integrations: work items and incidents

> Create a work item, create an incident and create a project in Axosoft. Connect Axosoft to the rest of your developer tools stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/axosoft-integrations/
**Categories:** Developer tools
**Connects through:** HTTP Connector

## Overview

Axosoft is agile project management software for development teams, covering sprint planning, bug tracking, help desk tickets, work logs and release tracking. Tray.ai connects to Axosoft through the HTTP Connector, so your workflows can call the Axosoft API alongside the rest of your stack.

## Use cases

### Work items

Read, create, update, and delete work items in Axosoft from any Tray.ai workflow. The Axosoft API covers calls such as list work items and create a work item.

- List work items
- Create a work item
- Update a work item

### Incidents

Read, create, update, and delete incidents in Axosoft from any Tray.ai workflow. The Axosoft API covers calls such as list incidents and create an incident.

- List incidents
- Create an incident
- Update an incident

### Projects

Read, create, update, and delete projects in Axosoft from any Tray.ai workflow. The Axosoft API covers calls such as list projects and get a project.

- List projects
- Get a project
- Create a project

### Work logs

Read, create, update, and delete work logs in Axosoft from any Tray.ai workflow. The Axosoft API covers calls such as list work logs and add a work log.

- List work logs
- Add a work log
- Update a work log

## Challenges Tray.ai solves

### Keeping Axosoft credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Axosoft credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Axosoft API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Axosoft API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Axosoft?

Yes. Tray.ai connects to Axosoft through the HTTP Connector, which calls the Axosoft API directly. Any call the Axosoft API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Axosoft?

The Axosoft API uses OAuth 2.0, a bearer token, and an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Axosoft connector?

Axosoft runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Axosoft connector from the Axosoft API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/