> For the complete documentation index, see [llms.txt](https://docs.valorx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valorx.com/valorx-fusion/design-studio/workflow-and-ux/api.md).

# API

**Application Program Interface (API)** apart form Step name if an API task is configured to have input from Data Intake then API properties will have Data Intakes section to select required Object data which is nothing but an output of other task. It can also have Output Name property only if Action selected in API task has return type Object.

Refer [**API**](/valorx-fusion/design-studio/tasks/api.md) to know how to create an API class.

Once an API query task is created it will display in the API workflow properties. Expand the API properties and you will find all the API classes. Designers needs to just drag and drop the API as per the app requirement.

![](/files/Ckq603VsavVACP9pcOvu)

On the right hand side Designers can find Edit API Task by clicking on it a window will open in which Designers can edit the API class. Designers can even select a button to display on the Ribbon from **Workflow Trigger**.

![](/files/bY1VebGcSiHRSPohXES0)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.valorx.com/valorx-fusion/design-studio/workflow-and-ux/api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.