Features API

Features belong to releases. This means that if you want to create one then you must scope it to a release.

You can return a result set which is unfiltered, or filter by release , product , or epic. All these means of listing features can be further filtered by specific criteria like name, modification date, tag, or assignee.

Once you have the id of a specific feature, you can inspect, modify, or delete them on the root features resource.

List features in a product

GET /api/v1/products/:product_id/features

Parameters
Name	Description
`page`	Page number to return.
`per_page`	Number of records to return per page.
`product_id *`	Numeric ID or key of the product
`q`	Search term to match against feature name
`updated_since`	UTC timestamp (in ISO8601 format). If provided, only features updated after the timestamp will be returned
`tag`	String tag value. If provided, only features with the associated tag will be returned
`assigned_to_user`	ID or email address of a user. If provided, only features assigned to that user will be returned
`workflow_status`	Workflow status ID or name. If provided, only features with that workflow status will be returned
`custom_fields`	Hash of custom field key-value pairs. If provided, only features matching all specified custom field values will be returned. Example: {"field_key": "field_value"}

Example request

GET /api/v1/products/PRJ1/features?page=1&per_page=30

Example CURL command

curl -g "https://company.aha.io/api/v1/products/PRJ1/features?page=1&per_page=30" -X GET \
	-H "Authorization: Bearer 15b60d42d4bc417284a246ced6877b0bf13fb4aca415f7b55f7006bc3694a8ab" \
	-H "Content-Type: application/json" \
	-H "Accept: application/json"

Request

authorization: Bearer 15b60d42d4bc417284a246ced6877b0bf13fb4aca415f7b55f7006bc3694a8ab
contentType: application/json
accept: application/json

Response

Status: 200 OK
contentType: application/json; charset=utf-8

Response body