# Asana Integration via LowCodeAPI

## Overview

Work management platform

## Base Endpoint

```
https://api.lowcodeapi.com/asana/
```

## Authentication

LowCodeAPI handles authentication automatically. You only need to:

1. **Sign up** at [https://asana.com](https://asana.com)
2. **Get your credentials** from [https://app.asana.com/0/my-apps](https://app.asana.com/0/my-apps)
3. **Connect your account** in LowCodeAPI dashboard
4. **Use your `api_token`** in all requests

The `api_token` is your LowCodeAPI authentication token. LowCodeAPI will automatically:
- Fetch your Asana API key
- Apply it to each request with `Authorization` header

**Auth Type**: API Key (Authorization header)

## API Categories

- Project Management

## Common Endpoints

### Category: Attachments

#### Get the full record for a single attachment

**Method**: `GET` | **LowCodeAPI Path**: `/attachments/attachment_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/attachments/attachment_gid?attachment_gid={attachment_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `attachment_gid` | string | Globally unique identifier for the attachment |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/attachments/attachment_gid?attachment_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getattachment](https://developers.asana.com/reference/getattachment)

---

#### Deletes a specific existing attachment

**Method**: `DELETE` | **LowCodeAPI Path**: `/attachments/attachment_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/attachments/attachment_gid?attachment_gid={attachment_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `attachment_gid` | string | Globally unique identifier for the attachment |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/attachments/attachment_gid?attachment_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deleteattachment](https://developers.asana.com/reference/deleteattachment)

---

#### Returns the compact records for all attachments on the object

**Method**: `GET` | **LowCodeAPI Path**: `/attachments`

**Full URL**:
```
https://api.lowcodeapi.com/asana/attachments?...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `parent` | string | Yes | Globally unique identifier for the parent object (task, project, etc.) to get attachments for |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/attachments?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getattachmentsforobject](https://developers.asana.com/reference/getattachmentsforobject)

---

#### Upload an attachment

**Method**: `POST` | **LowCodeAPI Path**: `/attachments`

**Full URL**:
```
https://api.lowcodeapi.com/asana/attachments?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Body Parameters**:

| `file` | file | Yes | The file to upload |
| `parent` | string | Yes | Globally unique identifier for the parent object (task, project, etc.) to attach the file to |
| `name` | string | No | The name of the file being uploaded |
| `connect_to_app` | boolean | No | Whether to connect the attachment to an app |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/attachments?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"file":"value","parent":"value","name":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createattachmentforobject](https://developers.asana.com/reference/createattachmentforobject)

---

### Category: Batch

#### Make multiple requests in parallel to Asana's API

**Method**: `POST` | **LowCodeAPI Path**: `/batch`

**Full URL**:
```
https://api.lowcodeapi.com/asana/batch?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Body Parameters**:

| `actions` | array | Yes | An array of actions to execute. Each action object must have a `relative_path` and `method` field, and optionally a `data` field. |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/batch?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"actions":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createbatchrequest](https://developers.asana.com/reference/createbatchrequest)

---

### Category: Custom Fields

#### Creates an enum option and adds it to this custom field’s list of enum options

**Method**: `POST` | **LowCodeAPI Path**: `/custom_fields/custom_field_gid/enum_options`

**Full URL**:
```
https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid/enum_options?custom_field_gid={custom_field_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `custom_field_gid` | string | Globally unique identifier for the custom field |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | Yes | The enum option object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid/enum_options?custom_field_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createenumoptionforcustomfield](https://developers.asana.com/reference/createenumoptionforcustomfield)

---

#### Moves a particular enum option to be either before or after another specified enum option in the custom field

**Method**: `POST` | **LowCodeAPI Path**: `/custom_fields/custom_field_gid/enum_options/insert`

**Full URL**:
```
https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid/enum_options/insert?custom_field_gid={custom_field_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `custom_field_gid` | string | Globally unique identifier for the custom field |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | Yes | The enum option object with position information |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid/enum_options/insert?custom_field_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/insertenumoptionforcustomfield](https://developers.asana.com/reference/insertenumoptionforcustomfield)

---

#### Get the complete definition of a custom field’s metadata

**Method**: `GET` | **LowCodeAPI Path**: `/custom_fields/custom_field_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid?custom_field_gid={custom_field_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `custom_field_gid` | string | Globally unique identifier for the custom field |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid?custom_field_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getcustomfield](https://developers.asana.com/reference/getcustomfield)

---

#### A specific existing custom field can be updated by making a PUT request on the URL for that custom field

**Method**: `PUT` | **LowCodeAPI Path**: `/custom_fields/custom_field_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid?custom_field_gid={custom_field_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `custom_field_gid` | string | Globally unique identifier for the custom field |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The custom field object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid?custom_field_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updatecustomfield](https://developers.asana.com/reference/updatecustomfield)

---

#### A specific existing custom field can be deleted by making a DELETE request on the URL for that custom field

**Method**: `DELETE` | **LowCodeAPI Path**: `/custom_fields/custom_field_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid?custom_field_gid={custom_field_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `custom_field_gid` | string | Globally unique identifier for the custom field |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/custom_fields/custom_field_gid?custom_field_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deletecustomfield](https://developers.asana.com/reference/deletecustomfield)

---

#### Creates a new custom field in a workspace

**Method**: `POST` | **LowCodeAPI Path**: `/custom_fields`

**Full URL**:
```
https://api.lowcodeapi.com/asana/custom_fields?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Body Parameters**:

| `data` | object | Yes | The custom field object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/custom_fields?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createcustomfield](https://developers.asana.com/reference/createcustomfield)

---

### Category: Enum Options

#### Updates an existing enum option

**Method**: `PUT` | **LowCodeAPI Path**: `/enum_options/enum_option_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/enum_options/enum_option_gid?enum_option_gid={enum_option_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `enum_option_gid` | string | Globally unique identifier for the enum option |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/enum_options/enum_option_gid?enum_option_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/updateEnumoption](https://developers.asana.com/reference/updateEnumoption)

---

### Category: Events

#### Returns the full record for all events that have occurred since the sync

**Method**: `GET` | **LowCodeAPI Path**: `/events`

**Full URL**:
```
https://api.lowcodeapi.com/asana/events?...&api_token={api_token}
```


**Query Parameters**:

| `resource` | string | No |  |
| `sync` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/events?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getevents](https://developers.asana.com/reference/getevents)

---

### Category: Goal Relationships

#### Returns the complete updated goal relationship record for a single goal relationship

**Method**: `GET` | **LowCodeAPI Path**: `/goal_relationships/goal_relationship_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goal_relationships/goal_relationship_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/goal_relationships/goal_relationship_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getGoalrelationship](https://developers.asana.com/reference/getGoalrelationship)

---

#### An existing goal relationship can be updated by making a PUT request on the URL for

**Method**: `PUT` | **LowCodeAPI Path**: `/goal_relationships/goal_relationship_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goal_relationships/goal_relationship_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/goal_relationships/goal_relationship_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/updateGoalrelationship](https://developers.asana.com/reference/updateGoalrelationship)

---

#### Returns compact goal relationship records

**Method**: `GET` | **LowCodeAPI Path**: `/goal_relationships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goal_relationships?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `supported_goal` | string | No |  |
| `resource_subtype` | string | No |  |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/goal_relationships?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getGoalrelationships](https://developers.asana.com/reference/getGoalrelationships)

---

### Category: Goals

#### Returns the complete goal record for a single goal

**Method**: `GET` | **LowCodeAPI Path**: `/goals/goal_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/goals/goal_gid?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getgoal](https://developers.asana.com/reference/getgoal)

---

#### An existing goal can be updated by making a PUT request on the URL for

**Method**: `PUT` | **LowCodeAPI Path**: `/goals/goal_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The goal object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/goals/goal_gid?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updategoal](https://developers.asana.com/reference/updategoal)

---

#### A specific existing goal can be deleted by making a DELETE request on the URL for that goal

**Method**: `DELETE` | **LowCodeAPI Path**: `/goals/goal_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/goals/goal_gid?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deletegoal](https://developers.asana.com/reference/deletegoal)

---

#### Creates a goal relationship by adding a supporting resource to a given goal

**Method**: `POST` | **LowCodeAPI Path**: `/goals/goal_gid/addsupportingrelationship`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid/addsupportingrelationship?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/goals/goal_gid/addsupportingrelationship?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAddsupportingrelationship](https://developers.asana.com/reference/createAddsupportingrelationship)

---

#### Removes a goal relationship for a given parent goal

**Method**: `POST` | **LowCodeAPI Path**: `/goals/goal_gid/removesupportingrelationship`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid/removesupportingrelationship?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/goals/goal_gid/removesupportingrelationship?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createRemovesupportingrelationship](https://developers.asana.com/reference/createRemovesupportingrelationship)

---

#### Creates and adds a goal metric to a specified goal

**Method**: `POST` | **LowCodeAPI Path**: `/goals/goal_gid/setmetric`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid/setmetric?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/goals/goal_gid/setmetric?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createSetmetric](https://developers.asana.com/reference/createSetmetric)

---

#### Updates a goal's existing metric's `current_number_value` if one exists

**Method**: `POST` | **LowCodeAPI Path**: `/goals/goal_gid/setmetriccurrentvalue`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid/setmetriccurrentvalue?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/goals/goal_gid/setmetriccurrentvalue?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createSetmetriccurrentvalue](https://developers.asana.com/reference/createSetmetriccurrentvalue)

---

#### Adds followers to a goal

**Method**: `POST` | **LowCodeAPI Path**: `/goals/goal_gid/addfollowers`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid/addfollowers?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/goals/goal_gid/addfollowers?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAddfollowers](https://developers.asana.com/reference/createAddfollowers)

---

#### Removes followers from a goal

**Method**: `POST` | **LowCodeAPI Path**: `/goals/goal_gid/removefollowers`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid/removefollowers?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/goals/goal_gid/removefollowers?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createRemovefollowers](https://developers.asana.com/reference/createRemovefollowers)

---

#### Returns a compact representation of all of the parent goals of a goal

**Method**: `GET` | **LowCodeAPI Path**: `/goals/goal_gid/parentgoals`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals/goal_gid/parentgoals?goal_gid={goal_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `goal_gid` | string | Globally unique identifier for the goal |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/goals/goal_gid/parentgoals?goal_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getParentgoals](https://developers.asana.com/reference/getParentgoals)

---

#### Returns compact goal records

**Method**: `GET` | **LowCodeAPI Path**: `/goals`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals?...&api_token={api_token}
```


**Query Parameters**:

| `portfolio` | string | No |  |
| `project` | string | No |  |
| `is_workspace_level` | string | No |  |
| `team` | string | No |  |
| `workspace` | string | No |  |
| `time_periods` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/goals?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/creategoal](https://developers.asana.com/reference/creategoal)

---

#### Creates a new goal in a workspace or team

**Method**: `POST` | **LowCodeAPI Path**: `/goals`

**Full URL**:
```
https://api.lowcodeapi.com/asana/goals?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Body Parameters**:

| `data` | object | Yes | The goal object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/goals?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/creategoal](https://developers.asana.com/reference/creategoal)

---

### Category: Jobs

#### Returns the full record for a job

**Method**: `GET` | **LowCodeAPI Path**: `/jobs/job_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/jobs/job_gid?job_gid={job_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `job_gid` | string | Globally unique identifier for the job |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/jobs/job_gid?job_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getjob](https://developers.asana.com/reference/getjob)

---

### Category: Memberships

#### A specific existing membership can be deleted by making a `DELETE` request

**Method**: `DELETE` | **LowCodeAPI Path**: `/memberships/membership_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/memberships/membership_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/memberships/membership_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deleteMembership](https://developers.asana.com/reference/deleteMembership)

---

#### An existing membership can be updated by making a `PUT` request on the URL for that goal

**Method**: `PUT` | **LowCodeAPI Path**: `/memberships/membership_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/memberships/membership_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/memberships/membership_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/updateMembership](https://developers.asana.com/reference/updateMembership)

---

#### Returns compact membership records

**Method**: `GET` | **LowCodeAPI Path**: `/memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/memberships?...&api_token={api_token}
```


**Query Parameters**:

| `parent` | string | No |  |
| `member` | string | No |  |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/memberships?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getMemberships](https://developers.asana.com/reference/getMemberships)

---

#### Creates a new membership in a `team` `project` `goal` or `portfolio`

**Method**: `POST` | **LowCodeAPI Path**: `/memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/memberships?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/memberships?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createMemberships](https://developers.asana.com/reference/createMemberships)

---

### Category: Organization Exports

#### This method creates a request to export an Organization

**Method**: `POST` | **LowCodeAPI Path**: `/organization_exports`

**Full URL**:
```
https://api.lowcodeapi.com/asana/organization_exports?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Body Parameters**:

| `data` | object | Yes | The organization export object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/organization_exports?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createorganizationexport](https://developers.asana.com/reference/createorganizationexport)

---

#### Returns details of a previously-requested Organization export

**Method**: `GET` | **LowCodeAPI Path**: `/organization_exports/organization_export_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/organization_exports/organization_export_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/organization_exports/organization_export_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getorganizationexport](https://developers.asana.com/reference/getorganizationexport)

---

### Category: Portfolio Memberships

#### Returns a list of portfolio memberships in compact representation

**Method**: `GET` | **LowCodeAPI Path**: `/portfolio_memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolio_memberships?...&api_token={api_token}
```


**Query Parameters**:

| `portfolio` | string | No |  |
| `workspace` | string | No |  |
| `user` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/portfolio_memberships?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getPortfoliomemberships](https://developers.asana.com/reference/getPortfoliomemberships)

---

#### Returns the complete portfolio record for a single portfolio membership

**Method**: `GET` | **LowCodeAPI Path**: `/portfolio_memberships/portfolio_membership_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolio_memberships/portfolio_membership_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/portfolio_memberships/portfolio_membership_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getPortfoliomembership](https://developers.asana.com/reference/getPortfoliomembership)

---

### Category: Portfolios

#### Returns the complete portfolio record for a single portfolio

**Method**: `GET` | **LowCodeAPI Path**: `/portfolios/portfolio_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getportfolio](https://developers.asana.com/reference/getportfolio)

---

#### An existing portfolio can be updated by making a PUT request on the URL for

**Method**: `PUT` | **LowCodeAPI Path**: `/portfolios/portfolio_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The portfolio object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updateportfolio](https://developers.asana.com/reference/updateportfolio)

---

#### An existing portfolio can be deleted by making a DELETE request on

**Method**: `DELETE` | **LowCodeAPI Path**: `/portfolios/portfolio_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deleteportfolio](https://developers.asana.com/reference/deleteportfolio)

---

#### Returns a list of all of the custom fields settings on a portfolio in compact form

**Method**: `GET` | **LowCodeAPI Path**: `/portfolios/portfolio_gid/custom_field_settings`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/custom_field_settings?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/custom_field_settings?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getCustomfieldsettings](https://developers.asana.com/reference/getCustomfieldsettings)

---

#### Returns the compact portfolio membership records for the portfolio

**Method**: `GET` | **LowCodeAPI Path**: `/portfolios/portfolio_gid/portfolio_memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/portfolio_memberships?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `user` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/portfolio_memberships?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getPortfoliomemberships](https://developers.asana.com/reference/getPortfoliomemberships)

---

#### Get a list of the items in compact form in a portfolio

**Method**: `GET` | **LowCodeAPI Path**: `/portfolios/portfolio_gid/items`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/items?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/items?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getItems](https://developers.asana.com/reference/getItems)

---

#### Add an item to a portfolio

**Method**: `POST` | **LowCodeAPI Path**: `/portfolios/portfolio_gid/additem`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/additem?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/additem?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAdditem](https://developers.asana.com/reference/createAdditem)

---

#### Remove an item from a portfolio

**Method**: `POST` | **LowCodeAPI Path**: `/portfolios/portfolio_gid/removeitem`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/removeitem?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/removeitem?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createRemoveitem](https://developers.asana.com/reference/createRemoveitem)

---

#### Custom fields are associated with portfolios by way of custom field settings

**Method**: `POST` | **LowCodeAPI Path**: `/portfolios/portfolio_gid/addcustomfieldsetting`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/addcustomfieldsetting?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/addcustomfieldsetting?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAddcustomfieldsetting](https://developers.asana.com/reference/createAddcustomfieldsetting)

---

#### Removes a custom field setting from a portfolio

**Method**: `POST` | **LowCodeAPI Path**: `/portfolios/portfolio_gid/removecustomfieldsetting`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/removecustomfieldsetting?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/removecustomfieldsetting?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createRemovecustomfieldsetting](https://developers.asana.com/reference/createRemovecustomfieldsetting)

---

#### Adds the specified list of users as members of the portfolio

**Method**: `POST` | **LowCodeAPI Path**: `/portfolios/portfolio_gid/addmembers`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/addmembers?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/addmembers?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAddmembers](https://developers.asana.com/reference/createAddmembers)

---

#### Removes the specified list of users from members of the portfolio

**Method**: `POST` | **LowCodeAPI Path**: `/portfolios/portfolio_gid/removemembers`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/removemembers?portfolio_gid={portfolio_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `portfolio_gid` | string | Globally unique identifier for the portfolio |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/portfolios/portfolio_gid/removemembers?portfolio_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createRemovemembers](https://developers.asana.com/reference/createRemovemembers)

---

#### Returns a list of the portfolios in compact representation that are owned by the current API user

**Method**: `GET` | **LowCodeAPI Path**: `/portfolios`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios?...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `workspace` | string | No |  |
| `owner` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/portfolios?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createportfolio](https://developers.asana.com/reference/createportfolio)

---

#### Creates a new portfolio in the given workspace with the supplied name

**Method**: `POST` | **LowCodeAPI Path**: `/portfolios`

**Full URL**:
```
https://api.lowcodeapi.com/asana/portfolios?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Body Parameters**:

| `data` | object | Yes | The portfolio object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/portfolios?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createportfolio](https://developers.asana.com/reference/createportfolio)

---

### Category: Project Briefs

#### Get the full record for a project brief

**Method**: `GET` | **LowCodeAPI Path**: `/project_briefs/project_brief_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/project_briefs/project_brief_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/project_briefs/project_brief_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getprojectbrief](https://developers.asana.com/reference/getprojectbrief)

---

#### An existing project brief can be updated by making a PUT request on the URL for

**Method**: `PUT` | **LowCodeAPI Path**: `/project_briefs/project_brief_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/project_briefs/project_brief_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Body Parameters**:

| `data` | object | No | The project brief object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/project_briefs/project_brief_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updateprojectbrief](https://developers.asana.com/reference/updateprojectbrief)

---

#### Deletes a specific existing project brief

**Method**: `DELETE` | **LowCodeAPI Path**: `/project_briefs/project_brief_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/project_briefs/project_brief_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/project_briefs/project_brief_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deleteprojectbrief](https://developers.asana.com/reference/deleteprojectbrief)

---

### Category: Project Membership

#### Returns the complete project record for a single project membership

**Method**: `GET` | **LowCodeAPI Path**: `/project_memberships/project_membership_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/project_memberships/project_membership_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/project_memberships/project_membership_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getProjectmembership](https://developers.asana.com/reference/getProjectmembership)

---

### Category: Project Statuses

#### *Deprecated: new integrations should prefer the `/status_updates/{status_gid}` route

**Method**: `GET` | **LowCodeAPI Path**: `/project_statuses/project_status_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/project_statuses/project_status_gid?project_status_gid={project_status_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_status_gid` | string | Globally unique identifier for the project status |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/project_statuses/project_status_gid?project_status_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getprojectstatus](https://developers.asana.com/reference/getprojectstatus)

---

#### *Deprecated: new integrations should prefer the `/status_updates/{status_gid}` route

**Method**: `DELETE` | **LowCodeAPI Path**: `/project_statuses/project_status_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/project_statuses/project_status_gid?project_status_gid={project_status_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_status_gid` | string | Globally unique identifier for the project status |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/project_statuses/project_status_gid?project_status_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deleteprojectstatus](https://developers.asana.com/reference/deleteprojectstatus)

---

### Category: Project Templates

#### Returns the complete project template record for a single project template

**Method**: `GET` | **LowCodeAPI Path**: `/project_templates/project_template_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/project_templates/project_template_gid?project_template_gid={project_template_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_template_gid` | string | Globally unique identifier for the project template |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/project_templates/project_template_gid?project_template_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getprojecttemplate](https://developers.asana.com/reference/getprojecttemplate)

---

#### Creates and returns a job that will asynchronously handle the project instantiation

**Method**: `POST` | **LowCodeAPI Path**: `/project_templates/project_template_gid/instantiateproject`

**Full URL**:
```
https://api.lowcodeapi.com/asana/project_templates/project_template_gid/instantiateproject?project_template_gid={project_template_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_template_gid` | string | Globally unique identifier for the project template |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/project_templates/project_template_gid/instantiateproject?project_template_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createInstantiateproject](https://developers.asana.com/reference/createInstantiateproject)

---

#### Returns the compact project template records for all project templates in the given team or workspace

**Method**: `GET` | **LowCodeAPI Path**: `/project_templates`

**Full URL**:
```
https://api.lowcodeapi.com/asana/project_templates?...&api_token={api_token}
```


**Query Parameters**:

| `workspace` | string | No |  |
| `team` | string | No |  |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/project_templates?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getprojecttemplates](https://developers.asana.com/reference/getprojecttemplates)

---

### Category: Projects

#### *Deprecated: new integrations should prefer the `/status_updates` route

**Method**: `GET` | **LowCodeAPI Path**: `/projects/project_gid/project_statuses`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/project_statuses?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/projects/project_gid/project_statuses?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getprojectstatusesforproject](https://developers.asana.com/reference/getprojectstatusesforproject)

---

#### *Deprecated: new integrations should prefer the `/status_updates` route

**Method**: `POST` | **LowCodeAPI Path**: `/projects/project_gid/project_statuses`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/project_statuses?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | Yes | The project status object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/projects/project_gid/project_statuses?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createprojectstatusforproject](https://developers.asana.com/reference/createprojectstatusforproject)

---

#### Returns the compact records for all sections in the specified project

**Method**: `GET` | **LowCodeAPI Path**: `/projects/project_gid/sections`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/sections?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/projects/project_gid/sections?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getsectionsforproject](https://developers.asana.com/reference/getsectionsforproject)

---

#### Creates a new section in a project

**Method**: `POST` | **LowCodeAPI Path**: `/projects/project_gid/sections`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/sections?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | Yes | The section object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/projects/project_gid/sections?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createsectionforproject](https://developers.asana.com/reference/createsectionforproject)

---

#### Move sections relative to each other

**Method**: `POST` | **LowCodeAPI Path**: `/projects/project_gid/sections/insert`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/sections/insert?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | Yes | The section object with position information |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/projects/project_gid/sections/insert?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/insertsectionforproject](https://developers.asana.com/reference/insertsectionforproject)

---

#### Returns the complete project record for a single project

**Method**: `GET` | **LowCodeAPI Path**: `/projects/project_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/projects/project_gid?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getproject](https://developers.asana.com/reference/getproject)

---

#### A specific existing project can be updated by making a PUT request on

**Method**: `PUT` | **LowCodeAPI Path**: `/projects/project_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The project object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/projects/project_gid?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updateproject](https://developers.asana.com/reference/updateproject)

---

#### A specific existing project can be deleted by making a DELETE request on

**Method**: `DELETE` | **LowCodeAPI Path**: `/projects/project_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/projects/project_gid?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deleteproject](https://developers.asana.com/reference/deleteproject)

---

#### Returns a list of all of the custom fields settings on a project in compact form

**Method**: `GET` | **LowCodeAPI Path**: `/projects/project_gid/custom_field_settings`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/custom_field_settings?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/projects/project_gid/custom_field_settings?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getCustomfieldsettings](https://developers.asana.com/reference/getCustomfieldsettings)

---

#### Creates a new project brief

**Method**: `POST` | **LowCodeAPI Path**: `/projects/project_gid/project_briefs`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/project_briefs?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/projects/project_gid/project_briefs?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createProjectbriefs](https://developers.asana.com/reference/createProjectbriefs)

---

#### Returns the compact project membership records for the project

**Method**: `GET` | **LowCodeAPI Path**: `/projects/project_gid/project_memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/project_memberships?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `user` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/projects/project_gid/project_memberships?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getProjectmemberships](https://developers.asana.com/reference/getProjectmemberships)

---

#### Creates and returns a job that will asynchronously handle the duplication

**Method**: `POST` | **LowCodeAPI Path**: `/projects/project_gid/duplicate`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/duplicate?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/projects/project_gid/duplicate?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createDuplicate](https://developers.asana.com/reference/createDuplicate)

---

#### Custom fields are associated with projects by way of custom field settings

**Method**: `POST` | **LowCodeAPI Path**: `/projects/project_gid/addcustomfieldsetting`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/addcustomfieldsetting?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/projects/project_gid/addcustomfieldsetting?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAddcustomfieldsetting](https://developers.asana.com/reference/createAddcustomfieldsetting)

---

#### Removes a custom field setting from a project

**Method**: `POST` | **LowCodeAPI Path**: `/projects/project_gid/removecustomfieldsetting`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/removecustomfieldsetting?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/projects/project_gid/removecustomfieldsetting?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createRemovecustomfieldsetting](https://developers.asana.com/reference/createRemovecustomfieldsetting)

---

#### Get an object that holds task count fields

**Method**: `GET` | **LowCodeAPI Path**: `/projects/project_gid/task_counts`

**Full URL**:
```
https://api.lowcodeapi.com/asana/projects/project_gid/task_counts?project_gid={project_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `project_gid` | string | Globally unique identifier for the project |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/projects/project_gid/task_counts?project_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getTaskcounts](https://developers.asana.com/reference/getTaskcounts)

---

### Category: Sections

#### Returns the complete record for a single section

**Method**: `GET` | **LowCodeAPI Path**: `/sections/section_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/sections/section_gid?section_gid={section_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `section_gid` | string | Globally unique identifier for the section |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/sections/section_gid?section_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getsection](https://developers.asana.com/reference/getsection)

---

#### A specific existing section can be updated by making a PUT request on

**Method**: `PUT` | **LowCodeAPI Path**: `/sections/section_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/sections/section_gid?section_gid={section_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `section_gid` | string | Globally unique identifier for the section |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The section object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/sections/section_gid?section_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updatesection](https://developers.asana.com/reference/updatesection)

---

#### A specific existing section can be deleted by making a DELETE request on

**Method**: `DELETE` | **LowCodeAPI Path**: `/sections/section_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/sections/section_gid?section_gid={section_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `section_gid` | string | Globally unique identifier for the section |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/sections/section_gid?section_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deletesection](https://developers.asana.com/reference/deletesection)

---

#### Add a task to a specific existing section

**Method**: `POST` | **LowCodeAPI Path**: `/sections/section_gid/addtask`

**Full URL**:
```
https://api.lowcodeapi.com/asana/sections/section_gid/addtask?section_gid={section_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `section_gid` | string | Globally unique identifier for the section |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/sections/section_gid/addtask?section_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAddtask](https://developers.asana.com/reference/createAddtask)

---

#### *Board view only*: Returns the compact section records for all tasks within the given section

**Method**: `GET` | **LowCodeAPI Path**: `/sections/section_gid/tasks`

**Full URL**:
```
https://api.lowcodeapi.com/asana/sections/section_gid/tasks?section_gid={section_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `section_gid` | string | Globally unique identifier for the section |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/sections/section_gid/tasks?section_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/gettasksforsection](https://developers.asana.com/reference/gettasksforsection)

---

### Category: Status Updates

#### Returns the complete record for a single status update

**Method**: `GET` | **LowCodeAPI Path**: `/status_updates/status_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/status_updates/status_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/status_updates/status_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getStatus](https://developers.asana.com/reference/getStatus)

---

#### Deletes a specific existing status update

**Method**: `DELETE` | **LowCodeAPI Path**: `/status_updates/status_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/status_updates/status_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/status_updates/status_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deleteStatus](https://developers.asana.com/reference/deleteStatus)

---

#### Returns the compact status update records for all updates on the object

**Method**: `GET` | **LowCodeAPI Path**: `/status_updates`

**Full URL**:
```
https://api.lowcodeapi.com/asana/status_updates?...&api_token={api_token}
```


**Query Parameters**:

| `parent` | string | No |  |
| `created_since` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/status_updates?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createstatusupdate](https://developers.asana.com/reference/createstatusupdate)

---

#### Creates a new status update on an object

**Method**: `POST` | **LowCodeAPI Path**: `/status_updates`

**Full URL**:
```
https://api.lowcodeapi.com/asana/status_updates?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Body Parameters**:

| `data` | object | Yes | The status update object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/status_updates?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createstatusupdate](https://developers.asana.com/reference/createstatusupdate)

---

### Category: Stories

#### Returns the full record for a single story

**Method**: `GET` | **LowCodeAPI Path**: `/stories/story_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/stories/story_gid?story_gid={story_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `story_gid` | string | Globally unique identifier for the story |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/stories/story_gid?story_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getstory](https://developers.asana.com/reference/getstory)

---

#### Updates the story and returns the full record for the updated story

**Method**: `PUT` | **LowCodeAPI Path**: `/stories/story_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/stories/story_gid?story_gid={story_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `story_gid` | string | Globally unique identifier for the story |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The story object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/stories/story_gid?story_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updatestory](https://developers.asana.com/reference/updatestory)

---

#### Deletes a story

**Method**: `DELETE` | **LowCodeAPI Path**: `/stories/story_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/stories/story_gid?story_gid={story_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `story_gid` | string | Globally unique identifier for the story |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/stories/story_gid?story_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deletestory](https://developers.asana.com/reference/deletestory)

---

### Category: Tags

#### Returns the complete tag record for a single tag

**Method**: `GET` | **LowCodeAPI Path**: `/tags/tag_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tags/tag_gid?tag_gid={tag_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `tag_gid` | string | Globally unique identifier for the tag |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tags/tag_gid?tag_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/gettag](https://developers.asana.com/reference/gettag)

---

#### Updates the properties of a tag

**Method**: `PUT` | **LowCodeAPI Path**: `/tags/tag_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tags/tag_gid?tag_gid={tag_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `tag_gid` | string | Globally unique identifier for the tag |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The tag object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/tags/tag_gid?tag_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updatetag](https://developers.asana.com/reference/updatetag)

---

#### A specific existing tag can be deleted by making a DELETE request on

**Method**: `DELETE` | **LowCodeAPI Path**: `/tags/tag_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tags/tag_gid?tag_gid={tag_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `tag_gid` | string | Globally unique identifier for the tag |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/tags/tag_gid?tag_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deletetag](https://developers.asana.com/reference/deletetag)

---

#### Returns the compact task records for all tasks with the given tag

**Method**: `GET` | **LowCodeAPI Path**: `/tags/tag_gid/tasks`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tags/tag_gid/tasks?tag_gid={tag_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `tag_gid` | string | Globally unique identifier for the tag |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tags/tag_gid/tasks?tag_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/gettasksfortag](https://developers.asana.com/reference/gettasksfortag)

---

#### Returns the compact tag records for some filtered set of tags

**Method**: `GET` | **LowCodeAPI Path**: `/tags`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tags?...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `workspace` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tags?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createtag](https://developers.asana.com/reference/createtag)

---

#### Creates a new tag in a workspace or organization

**Method**: `POST` | **LowCodeAPI Path**: `/tags`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tags?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Body Parameters**:

| `data` | object | Yes | The tag object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/tags?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createtag](https://developers.asana.com/reference/createtag)

---

### Category: Tasks

#### Returns the compact records for all stories on the task

**Method**: `GET` | **LowCodeAPI Path**: `/tasks/task_gid/stories`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/stories?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tasks/task_gid/stories?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getstoriesfortask](https://developers.asana.com/reference/getstoriesfortask)

---

#### Adds a story to a task

**Method**: `POST` | **LowCodeAPI Path**: `/tasks/task_gid/stories`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/stories?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/tasks/task_gid/stories?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getstoriesfortask](https://developers.asana.com/reference/getstoriesfortask)

---

#### Returns a compact representation of all of the subtasks of a task

**Method**: `GET` | **LowCodeAPI Path**: `/tasks/task_gid/subtasks`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/subtasks?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tasks/task_gid/subtasks?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getsubtasksfortask](https://developers.asana.com/reference/getsubtasksfortask)

---

#### Creates a new subtask and adds it to the parent task

**Method**: `POST` | **LowCodeAPI Path**: `/tasks/task_gid/subtasks`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/subtasks?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/tasks/task_gid/subtasks?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getsubtasksfortask](https://developers.asana.com/reference/getsubtasksfortask)

---

#### Returns the complete task record for a single task

**Method**: `GET` | **LowCodeAPI Path**: `/tasks/task_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tasks/task_gid?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/gettask](https://developers.asana.com/reference/gettask)

---

#### A specific existing task can be updated by making a PUT request on the

**Method**: `PUT` | **LowCodeAPI Path**: `/tasks/task_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The task object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/tasks/task_gid?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updatetask](https://developers.asana.com/reference/updatetask)

---

#### A specific existing task can be deleted by making a DELETE request on

**Method**: `DELETE` | **LowCodeAPI Path**: `/tasks/task_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/tasks/task_gid?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deletetask](https://developers.asana.com/reference/deletetask)

---

#### Returns a compact representation of all of the projects the task is in

**Method**: `GET` | **LowCodeAPI Path**: `/tasks/task_gid/projects`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/projects?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tasks/task_gid/projects?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getProjects](https://developers.asana.com/reference/getProjects)

---

#### Get a compact representation of all of the tags the task has

**Method**: `GET` | **LowCodeAPI Path**: `/tasks/task_gid/tags`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/tags?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tasks/task_gid/tags?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getTags](https://developers.asana.com/reference/getTags)

---

#### Creates and returns a job that will asynchronously handle the duplication

**Method**: `POST` | **LowCodeAPI Path**: `/tasks/task_gid/duplicate`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/duplicate?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The duplicate options object |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/tasks/task_gid/duplicate?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/duplicatetask](https://developers.asana.com/reference/duplicatetask)

---

#### parent or no parent task at all

**Method**: `POST` | **LowCodeAPI Path**: `/tasks/task_gid/setparent`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/setparent?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/tasks/task_gid/setparent?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createSetparent](https://developers.asana.com/reference/createSetparent)

---

#### Returns the compact representations of all of the dependencies of a task

**Method**: `GET` | **LowCodeAPI Path**: `/tasks/task_gid/dependencies`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/dependencies?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tasks/task_gid/dependencies?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getDependencies](https://developers.asana.com/reference/getDependencies)

---

#### Marks a set of tasks as dependencies of this task if they are not already dependencies

**Method**: `POST` | **LowCodeAPI Path**: `/tasks/task_gid/adddependencies`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/adddependencies?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/tasks/task_gid/adddependencies?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAdddependencies](https://developers.asana.com/reference/createAdddependencies)

---

#### Unlinks a set of dependencies from this task

**Method**: `POST` | **LowCodeAPI Path**: `/tasks/task_gid/removedependencies`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/removedependencies?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/tasks/task_gid/removedependencies?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createRemovedependencies](https://developers.asana.com/reference/createRemovedependencies)

---

#### Returns the compact representations of all of the dependents of a task

**Method**: `GET` | **LowCodeAPI Path**: `/tasks/task_gid/dependents`

**Full URL**:
```
https://api.lowcodeapi.com/asana/tasks/task_gid/dependents?task_gid={task_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `task_gid` | string | Globally unique identifier for the task |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/tasks/task_gid/dependents?task_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getDependents](https://developers.asana.com/reference/getDependents)

---

### Category: Team Memberships

#### Returns compact team membership records

**Method**: `GET` | **LowCodeAPI Path**: `/team_memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/team_memberships?...&api_token={api_token}
```


**Query Parameters**:

| `team` | string | No |  |
| `user` | string | No |  |
| `workspace` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/team_memberships?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getTeammemberships](https://developers.asana.com/reference/getTeammemberships)

---

#### Returns the complete team membership record for a single team membership

**Method**: `GET` | **LowCodeAPI Path**: `/team_memberships/team_membership_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/team_memberships/team_membership_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/team_memberships/team_membership_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getTeammembership](https://developers.asana.com/reference/getTeammembership)

---

### Category: Teams

#### Returns the compact project records for all projects in the team

**Method**: `GET` | **LowCodeAPI Path**: `/teams/team_gid/projects`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams/team_gid/projects?team_gid={team_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `archived` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `team_gid` | string | Globally unique identifier for the team |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/teams/team_gid/projects?team_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getProjects](https://developers.asana.com/reference/getProjects)

---

#### Creates a project shared with the given team

**Method**: `POST` | **LowCodeAPI Path**: `/teams/team_gid/projects`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams/team_gid/projects?team_gid={team_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `team_gid` | string | Globally unique identifier for the team |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/teams/team_gid/projects?team_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createProjects](https://developers.asana.com/reference/createProjects)

---

#### Returns the full record for a single team

**Method**: `GET` | **LowCodeAPI Path**: `/teams/team_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams/team_gid?team_gid={team_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `team_gid` | string | Globally unique identifier for the team |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/teams/team_gid?team_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getteam](https://developers.asana.com/reference/getteam)

---

#### Returns the compact project template records for all project templates in the team

**Method**: `GET` | **LowCodeAPI Path**: `/teams/team_gid/project_templates`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams/team_gid/project_templates?team_gid={team_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `team_gid` | string | Globally unique identifier for the team |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/teams/team_gid/project_templates?team_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getProjecttemplates](https://developers.asana.com/reference/getProjecttemplates)

---

#### Returns the compact team memberships for the team

**Method**: `GET` | **LowCodeAPI Path**: `/teams/team_gid/team_memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams/team_gid/team_memberships?team_gid={team_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `team_gid` | string | Globally unique identifier for the team |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/teams/team_gid/team_memberships?team_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getTeammemberships](https://developers.asana.com/reference/getTeammemberships)

---

#### The user making this call must be a member of the team in order to add others

**Method**: `POST` | **LowCodeAPI Path**: `/teams/team_gid/adduser`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams/team_gid/adduser?team_gid={team_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `team_gid` | string | Globally unique identifier for the team |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/teams/team_gid/adduser?team_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAdduser](https://developers.asana.com/reference/createAdduser)

---

#### The user making this call must be a member of the team in order to remove themselves or others

**Method**: `POST` | **LowCodeAPI Path**: `/teams/team_gid/removeuser`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams/team_gid/removeuser?team_gid={team_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `team_gid` | string | Globally unique identifier for the team |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/teams/team_gid/removeuser?team_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createRemoveuser](https://developers.asana.com/reference/createRemoveuser)

---

#### Returns the compact records for all users that are members of the team

**Method**: `GET` | **LowCodeAPI Path**: `/teams/team_gid/users`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams/team_gid/users?team_gid={team_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `team_gid` | string | Globally unique identifier for the team |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/teams/team_gid/users?team_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getusersforteam](https://developers.asana.com/reference/getusersforteam)

---

#### Creates a team within the current workspace

**Method**: `POST` | **LowCodeAPI Path**: `/teams`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/teams?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getteams](https://developers.asana.com/reference/getteams)

---

#### Updates a team within the current workspace

**Method**: `PUT` | **LowCodeAPI Path**: `/teams`

**Full URL**:
```
https://api.lowcodeapi.com/asana/teams?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/teams?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getteams](https://developers.asana.com/reference/getteams)

---

### Category: Time Periods

#### Returns compact time period records

**Method**: `GET` | **LowCodeAPI Path**: `/time_periods`

**Full URL**:
```
https://api.lowcodeapi.com/asana/time_periods?...&api_token={api_token}
```


**Query Parameters**:

| `start_on` | string | No |  |
| `end_on` | string | No |  |
| `workspace` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/time_periods?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/gettimeperiods](https://developers.asana.com/reference/gettimeperiods)

---

#### Returns the full record for a single time period

**Method**: `GET` | **LowCodeAPI Path**: `/time_periods/time_period_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/time_periods/time_period_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/time_periods/time_period_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/gettimeperiod](https://developers.asana.com/reference/gettimeperiod)

---

### Category: User Task Lists

#### Returns the full record for a user task list

**Method**: `GET` | **LowCodeAPI Path**: `/user_task_lists/user_task_list_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/user_task_lists/user_task_list_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/user_task_lists/user_task_list_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getUsertasklist](https://developers.asana.com/reference/getUsertasklist)

---

#### Returns the compact list of tasks in a user’s My Tasks list

**Method**: `GET` | **LowCodeAPI Path**: `/user_task_lists/user_task_list_gid/tasks`

**Full URL**:
```
https://api.lowcodeapi.com/asana/user_task_lists/user_task_list_gid/tasks?...&api_token={api_token}
```


**Query Parameters**:

| `completed_since` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/user_task_lists/user_task_list_gid/tasks?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getTasks](https://developers.asana.com/reference/getTasks)

---

### Category: Users

#### Returns the full user record for the single user with the provided ID

**Method**: `GET` | **LowCodeAPI Path**: `/users/user_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/users/user_gid?user_gid={user_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `user_gid` | string | Globally unique identifier for the user |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/users/user_gid?user_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getuser](https://developers.asana.com/reference/getuser)

---

#### Returns the compact team membership records for the user

**Method**: `GET` | **LowCodeAPI Path**: `/users/user_gid/team_memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/users/user_gid/team_memberships?user_gid={user_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `workspace` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `user_gid` | string | Globally unique identifier for the user |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/users/user_gid/team_memberships?user_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getTeammemberships](https://developers.asana.com/reference/getTeammemberships)

---

#### Returns the compact records for all teams to which the given user is assigned

**Method**: `GET` | **LowCodeAPI Path**: `/users/user_gid/teams`

**Full URL**:
```
https://api.lowcodeapi.com/asana/users/user_gid/teams?user_gid={user_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `organization` | string | No |  |


**Path Parameters**:

| `user_gid` | string | Globally unique identifier for the user |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/users/user_gid/teams?user_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getteamsforuser](https://developers.asana.com/reference/getteamsforuser)

---

#### Returns the full record for a user's task list

**Method**: `GET` | **LowCodeAPI Path**: `/users/user_gid/user_task_list`

**Full URL**:
```
https://api.lowcodeapi.com/asana/users/user_gid/user_task_list?user_gid={user_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `workspace` | string | No |  |


**Path Parameters**:

| `user_gid` | string | Globally unique identifier for the user |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/users/user_gid/user_task_list?user_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getUsertasklist](https://developers.asana.com/reference/getUsertasklist)

---

#### Returns all of a user's favorites in the given workspace of the given type

**Method**: `GET` | **LowCodeAPI Path**: `/users/user_gid/favorites`

**Full URL**:
```
https://api.lowcodeapi.com/asana/users/user_gid/favorites?user_gid={user_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `resource_type` | string | No |  |
| `workspace` | string | No |  |


**Path Parameters**:

| `user_gid` | string | Globally unique identifier for the user |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/users/user_gid/favorites?user_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getFavorites](https://developers.asana.com/reference/getFavorites)

---

#### Returns the compact workspace membership records for the user

**Method**: `GET` | **LowCodeAPI Path**: `/users/user_gid/workspace_memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/users/user_gid/workspace_memberships?user_gid={user_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `user_gid` | string | Globally unique identifier for the user |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/users/user_gid/workspace_memberships?user_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getWorkspacememberships](https://developers.asana.com/reference/getWorkspacememberships)

---

#### Returns the user records for all users in all workspaces and organizations accessible to the authenticated user

**Method**: `GET` | **LowCodeAPI Path**: `/users`

**Full URL**:
```
https://api.lowcodeapi.com/asana/users?...&api_token={api_token}
```


**Query Parameters**:

| `workspace` | string | No |  |
| `team` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/users?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getusers](https://developers.asana.com/reference/getusers)

---

### Category: Webhooks

#### Returns the full record for the given webhook

**Method**: `GET` | **LowCodeAPI Path**: `/webhooks/webhook_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/webhooks/webhook_gid?webhook_gid={webhook_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `webhook_gid` | string | Globally unique identifier for the webhook |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/webhooks/webhook_gid?webhook_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getwebhook](https://developers.asana.com/reference/getwebhook)

---

#### An existing webhook's filters can be updated by making a PUT request on the URL for that webhook

**Method**: `PUT` | **LowCodeAPI Path**: `/webhooks/webhook_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/webhooks/webhook_gid?webhook_gid={webhook_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `webhook_gid` | string | Globally unique identifier for the webhook |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/webhooks/webhook_gid?webhook_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deletewebhook](https://developers.asana.com/reference/deletewebhook)

---

#### This method *permanently* removes a webhook

**Method**: `DELETE` | **LowCodeAPI Path**: `/webhooks/webhook_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/webhooks/webhook_gid?webhook_gid={webhook_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `webhook_gid` | string | Globally unique identifier for the webhook |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X DELETE "https://api.lowcodeapi.com/asana/webhooks/webhook_gid?webhook_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/deletewebhook](https://developers.asana.com/reference/deletewebhook)

---

#### Get the compact representation of all webhooks your app has registered for the authenticated user in the given workspace

**Method**: `GET` | **LowCodeAPI Path**: `/webhooks`

**Full URL**:
```
https://api.lowcodeapi.com/asana/webhooks?...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `workspace` | string | No |  |
| `resource` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/webhooks?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createwebhook](https://developers.asana.com/reference/createwebhook)

---

#### Establishing a webhook is a two-part process

**Method**: `POST` | **LowCodeAPI Path**: `/webhooks`

**Full URL**:
```
https://api.lowcodeapi.com/asana/webhooks?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Body Parameters**:

| `data` | object | Yes | The webhook object to create |


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/webhooks?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/createwebhook](https://developers.asana.com/reference/createwebhook)

---

### Category: Workspace Membership

#### Returns the complete workspace record for a single workspace membership

**Method**: `GET` | **LowCodeAPI Path**: `/workspace_memberships/workspace_membership_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspace_memberships/workspace_membership_gid?...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspace_memberships/workspace_membership_gid?...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getWorkspacemembership](https://developers.asana.com/reference/getWorkspacemembership)

---

### Category: Workspaces

#### Returns the compact project records for all projects in the workspace

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid/projects`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/projects?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `archived` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/projects?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getProjects](https://developers.asana.com/reference/getProjects)

---

#### Returns the compact project records for all projects in the workspace

**Method**: `POST` | **LowCodeAPI Path**: `/workspaces/workspace_gid/projects`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/projects?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/projects?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createProjects](https://developers.asana.com/reference/createProjects)

---

#### Returns the compact tag records for some filtered set of tags

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid/tags`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/tags?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/tags?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getTags](https://developers.asana.com/reference/getTags)

---

#### Creates a new tag in a workspace or organization

**Method**: `POST` | **LowCodeAPI Path**: `/workspaces/workspace_gid/tags`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/tags?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/tags?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createTags](https://developers.asana.com/reference/createTags)

---

#### Returns the full workspace record for a single workspace

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getworkspace](https://developers.asana.com/reference/getworkspace)

---

#### A specific existing workspace can be updated by making a PUT request on the URL for that workspace

**Method**: `PUT` | **LowCodeAPI Path**: `/workspaces/workspace_gid`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Body Parameters**:

| `data` | object | No | The workspace object to update |


**Example Request**:
```bash
curl -X PUT "https://api.lowcodeapi.com/asana/workspaces/workspace_gid?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"value"}'
```

**Official Documentation**: [https://developers.asana.com/reference/updateworkspace](https://developers.asana.com/reference/updateworkspace)

---

#### Retrieve the audit log events that have been captured in your domain

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid/audit_log_events`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/audit_log_events?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `start_at` | string | No |  |
| `end_at` | string | No |  |
| `event_type` | string | No |  |
| `actor_type` | string | No |  |
| `actor_gid` | string | No |  |
| `resource_gid` | string | No |  |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/audit_log_events?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getAuditlogevents](https://developers.asana.com/reference/getAuditlogevents)

---

#### Returns a list of the compact representation of all of the custom fields in a workspace

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid/custom_fields`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/custom_fields?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/custom_fields?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getCustomfields](https://developers.asana.com/reference/getCustomfields)

---

#### To mirror the functionality of the Asana web app's advanced search feature the Asana API has a task search endpoint that allows you to build complex filters to find and retrieve the exact data you need

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid/tasks/search`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/tasks/search?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `text` | string | No |  |
| `resource_subtype` | string | No |  |
| `assignee.any` | string | No |  |
| `assignee.not` | string | No |  |
| `portfolios.any` | string | No |  |
| `projects.any` | string | No |  |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/tasks/search?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getSearch](https://developers.asana.com/reference/getSearch)

---

#### Returns the compact records for all teams in the workspace visible to the authorized user

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid/teams`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/teams?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/teams?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getTeams](https://developers.asana.com/reference/getTeams)

---

#### Retrieves objects in the workspace based via an auto-completion/typeahead

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid/typeahead`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/typeahead?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `resource_type` | string | No |  |
| `type` | string | No |  |
| `query` | string | No |  |
| `count` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/typeahead?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/gettypeaheadforworkspace](https://developers.asana.com/reference/gettypeaheadforworkspace)

---

#### Returns the compact records for all users in the specified workspace or organization

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid/users`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/users?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/users?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getusersinworkspace](https://developers.asana.com/reference/getusersinworkspace)

---

#### Returns the compact workspace membership records for the workspace

**Method**: `GET` | **LowCodeAPI Path**: `/workspaces/workspace_gid/workspace_memberships`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/workspace_memberships?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `user` | string | No |  |
| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |
| `limit` | number | No | Results per page. The number of objects to return per page. The value must be between 1 and 100. |
| `offset` | string | No | Offset token. An offset to the next page returned by the API. A pagination request will return an offset token, and subsequent requests can use this token to retrieve the next page. If an offset is not passed in, the API will return the first page of results. Note that pagination tokens are only valid for a short period of time. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X GET "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/workspace_memberships?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/getworkspacemembershipsforworkspace](https://developers.asana.com/reference/getworkspacemembershipsforworkspace)

---

#### Add a user to a workspace or organization

**Method**: `POST` | **LowCodeAPI Path**: `/workspaces/workspace_gid/adduser`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/adduser?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/adduser?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createAdduser](https://developers.asana.com/reference/createAdduser)

---

#### Remove a user from a workspace or organization

**Method**: `POST` | **LowCodeAPI Path**: `/workspaces/workspace_gid/removeuser`

**Full URL**:
```
https://api.lowcodeapi.com/asana/workspaces/workspace_gid/removeuser?workspace_gid={workspace_gid}&...&api_token={api_token}
```


**Query Parameters**:

| `opt_pretty` | boolean | No | Provides "pretty" output. Provides the response in a "pretty" format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging. |
| `opt_fields` | string | No | Defines fields to return. Some requests return *compact* representations of objects in order to conserve resources and complete the request more efficiently. Other times requests return more information than you may need. This parameter allows you to list the exact set of fields that the API should be sure to return for the objects. The field names should be provided as paths, described below. The id of included objects will always be returned, regardless of the field options. |


**Path Parameters**:

| `workspace_gid` | string | Globally unique identifier for the workspace |

**Note**: Path parameters are passed in the URL path. The LowCodeAPI path uses static parameter names, and the actual values are passed as query parameters with the same names.


**Example Request**:
```bash
curl -X POST "https://api.lowcodeapi.com/asana/workspaces/workspace_gid/removeuser?workspace_gid=VALUE&...&api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
```

**Official Documentation**: [https://developers.asana.com/reference/createRemoveuser](https://developers.asana.com/reference/createRemoveuser)

---

## Usage Examples

### Example 1: Basic Usage

Get started with Asana API by making your first request.

```bash
# Your example code here
# This demonstrates basic usage
curl -X GET "https://api.lowcodeapi.com/asana/?api_token=YOUR_API_TOKEN"
```

### Example 2: Advanced Usage

Explore more advanced features and parameters.

```bash
# Your example code here
# This demonstrates advanced usage
curl -X GET "https://api.lowcodeapi.com/asana/?api_token=YOUR_API_TOKEN"
```

## Complete Endpoint Reference

For a complete list of all endpoints and their parameters, refer to:
- **OpenAPI Definition**: `https://backend.lowcodeapi.com/asana/definition`
- **Official Provider Documentation**: [https://developers.asana.com/reference](https://developers.asana.com/reference)

## Rate Limits & Best Practices

- Check your Asana account for specific rate limits
- Use appropriate error handling and retry logic
- Cache responses when appropriate to reduce API calls

## Error Handling

Standard HTTP status codes apply:
- `400` - Invalid request parameters
- `401` - Unauthorized (check your API key)
- `429` - Rate limit exceeded
- `500` - Internal server error