Expose integration data and enable field selection in Aha.io API for workflow automation

We're building automated release notes workflows that correlate Aha.io requirements with Azure DevOps Pull Requests. The current API has critical gaps that force manual work:

Gap 1: Integration Data Not Accessible

• The "Integrations" field (linked ADO work items) is visible in the web UI but NOT returned by the API

• See attached screenshot - requirement OYSTA-66-5 shows "User Story: 1930065" in UI, but GET /api/v1/requirements/OYSTA-66-5 doesn't return this data

• Forces us to manually open each requirement to copy work item IDs

Gap 2: No Field Selection

• API returns 50+ custom fields whether we need them or not

• Cannot request only the fields we need (e.g., just story_points and integrations)

• Results in large payloads and slow responses

Gap 3: No Bulk Operations

• Must make individual API calls for each requirement (20-50 per release)

• No way to get "all requirements in a release with their integrations" in one call

• Causes slow workflow execution and rate limiting

Gap 4: Cannot Filter by Custom Fields

• Cannot query "requirements where moscow=Must and fiscal_period=FY26Q3"

• Forces downloading everything and filtering client-side

Current manual process: 30-45 minutes per release

• Open each requirement in browser

• Copy integration ID

• Search Azure DevOps for linked PRs

• Compare PR content against acceptance criteria

• Write release notes

With API enhancements: 2 minutes, fully automated

• Single API call gets all requirements with integrations

• Automated PR correlation and validation

• AI-generated release notes

Time saved: 65-98 hours/year across our team
Quality improvement: 100% requirement coverage vs 60% currently

Enhancement 1: Add integrations field to API responses

Add to these endpoints:

• GET /api/v1/requirements/{id}

• GET /api/v1/features/{id}/requirements

• GET /api/v1/releases/{id}/features

Example response:

json

{
  "requirement": {
    "reference_num": "OYSTA-66-2",
    "integrations": [
      {
        "service": "azure_devops",
        "type": "user_story",
        "reference_num": "1930051",
        "url": "https://dev.azure.com/..."
      }
    ]
  }
}

Enhancement 2: Add field selection parameter

Enable requesting only needed fields:

GET /api/v1/requirements/{id}?fields=reference_num,name,integrations,acceptance_criteria

Enhancement 3: Add bulk endpoint

Get all requirements in release with one call:

GET /api/v1/releases/{id}/requirements?include=integrations,epic

Enhancement 4: Add custom field filtering

Query by custom field values:

GET /api/v1/requirements?custom_fields.moscow=Must&workflow_status=Testing

Example Workflow This Enables

Automated Release Notes Generation:

1. Call Aha API: Get release OYSTA-R-21 with all requirements and their ADO integrations (1 API call)

2. For each integration ID, call Azure DevOps API: Get linked PRs and code changes

3. Use AI to validate: PR content matches requirement acceptance criteria

4. Generate internal release notes (technical details, gaps)

5. Generate external release notes (customer-facing benefits)

6. Publish automatically

Current state: Impossible due to missing integration data
With enhancements: Fully automated in <2 minutes

Why This Matters

• Aha.io shows integration data in the UI but doesn't expose it via API - this is a fundamental gap

• Competitors (Jira, Azure DevOps) provide complete API access to all UI data

• Modern PM tools need robust APIs to support automation and AI workflows

• We're an enterprise customer committed to Aha long-term, but API gaps are blocking our investment in automation

Happy to beta test these enhancements and provide a case study on automated release management.