> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/automation/flow-builder/connectors-and-apis/wildcard-api-calls-and-actions.md).

# Wildcard API calls and actions

As of mid-October 2020, we started to include wildcard actions on each new Connector in order to give our customer full flexibility in creating end-points, that Locoia may not provide yet. The HTTP requests that are covered are:

* POST
* GET
* PUT
* PATCH
* DELETE

Just search for \`**wildcard**\` in the connector actions. If you don't find a wildcard action yet on a connector, we can add them in under 24 hours (business time) on any of the connectors.

{% hint style="info" %}
The **Endpoint** can be *relative* to the Connector base domain or you can pass an *absolute* URL in order to e.g. switch from api.myDomain.com/something to file.myDomain.com/upload
{% endhint %}

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48072774907/original/xiNj25_1ZarI164gdtc8o_yLll42qU9XWA.png?1606383285)

The individual fields offered on each wildcard action [render Jinja2 dynamically](/automation/flow-builder/jinja2-template-language.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.locoia.com/automation/flow-builder/connectors-and-apis/wildcard-api-calls-and-actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.