# Adding in Goal Type as a field in the goals-api

**URL:** <https://forum.asana.com/t/adding-in-goal-type-as-a-field-in-the-goals-api/1106969>\
**Category:** API & Developers\
**Tags:** goals\
**Created:** [4 November 2025 16:11 UTC](https://forum.asana.com/t/adding-in-goal-type-as-a-field-in-the-goals-api/1106969 "2025-11-04T16:11:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shahzeb\_Jiwani](https://luna1.co/8d76cd.png) [@Shahzeb\_Jiwani](https://forum.asana.com/u/Shahzeb_Jiwani)\
**Post date:** [4 November 2025 16:11 UTC](https://forum.asana.com/t/adding-in-goal-type-as-a-field-in-the-goals-api/1106969/1 "2025-11-04T16:11:00Z")

</div>

## Summary

Request to add a `goal_type` field to the Goals API that allows programmatic setting and updating of goal types (e.g., “Objective” vs standard goals) through API endpoints.

## Problem Statement

Currently, the Asana Goals API does not expose a `goal_type` or equivalent field that allows users to programmatically set whether a goal is an “Objective” type goal versus a standard goal. This functionality is available in the Asana web UI but is not accessible via the API.

This creates a workflow gap where:

1. Goals must be created via API for automation and scale

2. Goal types must then be manually updated in the UI

3. This breaks automation workflows and creates additional manual work

## Alternative Workarounds Considered

1. **Manual UI Updates:** Not scalable for organizations with many goals

2. **Using `is_workspace_level` flag:** Does not provide the same semantic meaning or UI display

3. **Naming conventions:** Prone to errors and doesn’t provide proper filtering/reporting

None of these provide the same functionality as native goal type support.

* * *

## Similar API Patterns

This request follows established Asana API patterns:

- Tasks have `resource_subtype` field (e.g., “default\_task”, “milestone”, “approval”)

- Projects have various type indicators

- Custom fields have `resource_subtype` to distinguish field types

Goals should similarly expose their type classification.

---

<div class="post-metadata">

**Author:** ![Dominik\_Brdak](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/dominik_brdak/32/281949_2.png) [@Dominik\_Brdak](https://forum.asana.com/u/Dominik_Brdak)\
**Post date:** [5 November 2025 10:10 UTC](https://forum.asana.com/t/adding-in-goal-type-as-a-field-in-the-goals-api/1106969/2 "2025-11-05T10:10:38Z")

</div>

Hi @Shazeb_Awab and welcome to the forum!

You’re right — that field isn’t currently exposed in the API. My guess is that it wasn’t initially included because it doesn’t directly affect the functionality of the goal itself. However, I can definitely see how it could be useful in certain use cases.

Your request sounds like great feedback for our API team. Could you please submit it through the [Developer Feedback Form](https://form-beta.asana.com/?k=LJh7rU8PrlRwLBl2a9JzwA&d=15793206719)? That’s the best way to make sure it reaches the right people for review and consideration.

Thanks for taking the time to share your thoughts and help improve Asana!

Best,  
Dominik

---

<div class="post-metadata">

**Author:** ![Mikhail\_Melikhov](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/mikhail_melikhov/32/288769_2.png) [@Mikhail\_Melikhov](https://forum.asana.com/u/Mikhail_Melikhov)\
**Post date:** [25 February 2026 14:34 UTC](https://forum.asana.com/t/adding-in-goal-type-as-a-field-in-the-goals-api/1106969/3 "2026-02-25T14:34:21Z")

</div>

The recommended and more flexible way to model this in the API is now Goal custom fields. With custom fields available on Goals, you can represent “Goal Type” as a single-select custom field, set ite, and read on it consistently, without needing a special-purpose core field.

This approach is also the direction taken to standardize on going forward, and over time we expect the legacy “goal type” concept to align with this model rather than expanding the API around the existing UI-only field.
