Axosoft API

Name: Axosoft API
Brand: Axosoft API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsProject Managementoauth247 EndpointsREST

For Agents

Manage Axosoft features, defects, incidents, projects, releases, and work logs from a single API. Suited to agents that automate Scrum and Kanban workflows for engineering teams.

Install Jentic One Beta

Connect the Axosoft API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Axosoft API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faxosoft.com%2Faxosoft" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faxosoft.com%2Faxosoft" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Axosoft API.

Create, list, retrieve, update, and delete features, defects, and incidents

Attach files and add comments to features, defects, and incidents

Move work items through workflow steps to advance Scrum or Kanban boards

GET STARTED

Start building with Axosoft API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Axosoft API for, with concrete tasks.

★ Bug Triage Automation

Support and engineering teams can route customer-reported bugs into Axosoft as defects via POST /defects, attach repro details with /defects/{id}/comments, and advance the workflow with /defects/{id}/workflow_steps. The /defects/{id}/attachments endpoint allows logs and screenshots to be attached for reproducers. Suited to teams shifting bug intake from email into a structured tracker.

POST /defects with the customer-reported bug summary and attach the support transcript via POST /defects/{id}/attachments

Feature Workflow and Release Management

Engineering managers can list features by project via GET /features, advance them through workflow steps with /features/{id}/workflow_steps, and tie them to /releases for release-train planning. The combination keeps board state and release scope aligned. Useful for teams running Scrum boards inside Axosoft.

PATCH a feature via POST /features/{id} to attach it to a release id, then transition it to 'Ready for QA' via POST /features/{id}/workflow_steps

Customer Incident Tracking

Support engineering can log customer-reported incidents through POST /incidents, link them to contacts, and tie related work via items. Comments and attachments capture investigation history. Suited to teams that handle production incidents inside their dev tracker rather than a separate tool.

POST /incidents with the customer description and contact id, then add the initial mitigation note via POST /incidents/{id}/comments

Time Tracking via Work Logs

Teams can record hours spent on items by posting to the work-logs endpoints, supporting time-tracked billing or capacity reporting. Combined with the items and projects endpoints, this gives a per-project effort view. Suited to consultancies and product teams that bill by hour or want capacity insight.

POST a work log entry tied to a specific feature id with hours and a description for the day's contribution

Agent-Driven Engineering Ops via Jentic

An engineering-ops agent can triage new defects, advance items through workflow steps, and pull release scope from Axosoft via Jentic without holding the OAuth client secret. Jentic exposes the feature, defect, incident, and release operations as discoverable tools. Suited to PM copilots and on-call assistants.

Search Jentic for 'list axosoft features', load GET /features, and execute it scoped to the current sprint to feed a status summary

Key Endpoints

47 endpoints — jentic publishes the only available openapi specification for axosoft api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/features

List features

POST

/features

Create a feature

POST

/features/{id}/workflow_steps

Advance a feature to a new workflow step

GET

/defects

List defects

POST

/defects

Create a defect

POST

/incidents

Create an incident

POST

/features/{id}/comments

Add a comment to a feature

GET

/features

List features

POST

/features

Create a feature

POST

/features/{id}/workflow_steps

Advance a feature to a new workflow step

GET

/defects

List defects

POST

/defects

Create a defect

POST

/incidents

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Axosoft by hand means running the OAuth 2.0 exchange, substituting your instance subdomain into the {instance}.axosoft.com/api/v6 host, and mapping item workflow transitions yourself. Through Jentic you install once, import the Axosoft API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

Axosoft puts the item id in the URL path (/features/{id}/..., /defects/{id}/...), so a rule can pin your agent to reading and commenting on those items. You choose the operations it may call, so destructive ones like deleting a defect or a feature are not included unless you add them.

Credential isolation

Your Axosoft OAuth client secret is stored once, encrypted, by your own Jentic One instance, which mints the short-lived access tokens scoped to your Axosoft instance at execution time. The raw client secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a defect in axosoft' or 'list features for a sprint', and Jentic returns the matching Axosoft operation with its input schema so the agent calls the right endpoint without walking the reference docs.

FAQs

Specific to using Axosoft API through Jentic.

Why is there no official OpenAPI spec for Axosoft API?

Axosoft does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Axosoft API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Axosoft API use?

Axosoft v6 uses OAuth 2.0. Through Jentic, the OAuth client secret is stored encrypted in the vault and the agent receives short-lived access tokens scoped to the Axosoft instance, so secrets never enter the agent context.

Can I create defects and advance their workflow with the Axosoft API?

Yes. POST /defects creates a defect, POST /defects/{id}/comments adds investigation notes, and POST /defects/{id}/workflow_steps moves the defect to a new workflow state.

How do I attach files to an Axosoft work item?

Use POST /features/{id}/attachments, POST /defects/{id}/attachments, or the equivalent /incidents path to upload an attachment tied to that item. The corresponding GET endpoints list existing attachments.

What are the rate limits for the Axosoft API?

The Axosoft OpenAPI spec does not declare published rate limits. Axosoft enforces instance-level quotas and OAuth scope limits; back off on 429 responses if encountered when iterating bulk operations.

How do I list features on a sprint through Jentic?

Search Jentic for 'list axosoft features', load GET /features, and execute it with a project filter. Jentic handles the OAuth token exchange and returns the feature list to your agent.

Can I limit what my agent is allowed to do with the Axosoft API?

Yes. Because you run Jentic One yourself, your own rules decide which Axosoft operations and credentials the agent may use. Axosoft puts the item id in the URL path (/features/{id}/..., /defects/{id}/...), so you can pin the agent to reading and commenting on specific items rather than the whole instance. You pick the exact operations it may call, so destructive ones like deleting a feature or defect stay out of reach unless you explicitly add them.

Axosoft API

Connect the Axosoft API to your agent

Capabilities

Start building with Axosoft API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs