# API Call

The "**API Call"** can be used at the beginning of the pipeline to read data from a certain API Endpoint and also at the end to send data to a certain external or internal API. API Endpoints are configured in the [integrations](/integrations/library-of-integrations/apis.md).

The task supports all the attributes of a normal API Call when it is done from the command line using `curl` or a software like `Postman`, such as body payload, headers, and query strings.

Here is an example of how to use it for sending some input data in the Body of the POST request:

<figure><img src="/files/L9qdrfSufKuUYTGdDdfQ" alt=""><figcaption></figcaption></figure>

You can also attach files, dynamically created from the input dataset to it. For example, if in front of the "**API call**" you place a "[Transformer](/pipelines/tasks-ip/transformers.md)" that converts input to CSV, the result can be sent further as a .csv file.

<div align="center"><figure><img src="/files/TU7IaK5qWGdskBV7WFrL" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: 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:

```
GET https://docs.ylem.co/pipelines/tasks-ip/api-call.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.