How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Aha.io Integration fields API

The Integration fields API from Aha.io — 15 operation(s) for integration fields.

Aha.io Integration fields API is one of 59 APIs that Aha.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Integration fields. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 15 operations across 15 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://{account-domain}.aha.io/api/v1.

15 operations 15 paths 5 schemas 1 DELETE9 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://{subdomain}.aha.io/api/v1
Authentication
OAuth 2.0, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

Aha.io Integration fields API declares 3 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow. It accepts HTTP bearer tokens (ApiKeyAuth). An API key is passed in the cookie as session (CookieAuth). By default, every request must be authenticated.

  • OAuth2 — OAuth2 authentication with bearer tokens
  • ApiKeyAuth — API key authentication using Bearer token in Authorization header. Generate API keys at https://secure.aha.io/settings/apikeys
  • CookieAuth — Cookie-based authentication for web browser integration

Paths & Operations 15

Across 15 paths, the API surfaces 15 operations — 1 DELETE, 9 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Integration fields 15
POST
/api/v1/features/{feature_id}/integrations/{integration_id}/fields
Create an integration field for a feature by integration ID
2 params body → 200
POST
/api/v1/features/{feature_id}/integrations/{service_name}/fields
Create an integration field for a feature by service name
2 params body → 200
POST
/api/v1/epics/{epic_id}/integrations/{integration_id}/fields
Create an integration field for a epic by integration ID
2 params body → 200
POST
/api/v1/idea_endorsements/{idea_endorsement_id}/integrations/{integration_id}/fields
Create an integration field for an idea vote
2 params body → 200
POST
/api/v1/ideas/{idea_id}/integrations/{integration_id}/fields
Create an integration field for an idea by integration ID
2 params body → 200
GET
/api/v1/features/{feature_id}/integrations/{integration_id}/fields/{field_name}
Get a specific integration field value
3 params → 200
GET
/api/v1/integrations/{integration_id}/fields/{field_name}/value/{field_value}
List records with an associated integration field value
3 params → 200
GET
/api/v1/releases/fields/{field_name}/value/{field_value}
List releases with an associated integration field value
2 params → 200
GET
/api/v1/initiatives/fields/{field_name}/value/{field_value}
List initiatives with an associated integration field value
2 params → 200
GET
/api/v1/features/fields/{field_name}/value/{field_value}
List features with an associated integration field value
2 params → 200
GET
/api/v1/epics/fields/{field_name}/value/{field_value}
List epics with an associated integration field value
2 params → 200
GET
/api/v1/requirements/fields/{field_name}/value/{field_value}
List requirements with an associated integration field value
2 params → 200
GET
/api/v1/ideas/fields/{field_name}/value/{field_value}
List ideas with an associated integration field value
2 params → 200
GET
/api/v1/idea_endorsements/fields/{field_name}/value/{field_value}
List idea votes with an associated integration field value
2 params → 200
DELETE
/api/v1/integration_fields/{id}
Delete an integration field
1 param → 204

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are IntegrationfieldsGetResponse (2 properties), IntegrationfieldsPostRequest (1 property), IntegrationfieldsPostResponse (1 property). Each schema is shown below with its type and property counts.

IntegrationfieldsPostResponse
object
1 property
IntegrationfieldsPostResponseArrayString
array
IntegrationfieldsGetResponse
object
2 properties
IntegrationfieldsPostResponseArrayInteger
array
IntegrationfieldsPostRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aha-integration-fields-api-openapi.yml Raw ↑

Other APIs Aha.io publishes across the network.

Aha.io Account backups API
Aha.io Attachments API
Aha.io Audits API
Aha.io Capacity estimate values API
Aha.io Capacity investments API
Aha.io Capacity scenarios API
Aha.io Comments API
Aha.io Competitors API
Aha.io Creative briefs API
Aha.io Custom field options API
Aha.io Custom fields API
Aha.io Custom Layouts API
Where this information came from

This is an independent, third-party profile of Aha.io Integration fields API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.