> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/app-components/connections.md).
# Connections
APIs usually use authentication or authorization to limit access to their endpoints.
Make provides a list of the most common types of connections with prefilled code that can be edited for your needs. In general, you will only need to change the URLs and names of the parameters.
## Types of connections
* [Basic connection](/custom-apps-documentation/app-components/connections/basic-connection.md)
* [JWT](/custom-apps-documentation/app-components/connections/jwt.md)
* [OAuth 1.0](/custom-apps-documentation/app-components/connections/oauth1.md)
* [OAuth 2.0](/custom-apps-documentation/app-components/connections/oauth2.md)
## Common data
When you use an OAuth connection, an ID and secret are generated for your user. To store them, you should use the common data inside the connection.
{% hint style="danger" %}
Make sure nobody else knows the client secret. Otherwise, your app can become vulnerable.
{% endhint %}
{% hint style="info" %}
When you need the common data to be available to all modules, use the [app's common data](/custom-apps-documentation/app-components/base.md#common-data) in the base instead.
{% endhint %}
Once the app is approved, the common data is locked and can't be changed due to security reasons.
Inside the connection, common data can be accessed by the `common.variable` IML expression.
Common data is encrypted when stored in Make.
## Reserved words in connections
Reserved words are variables used internally by Make. Using reserved words for the parameter `name` key can lead to unexpected results. Avoid using a reserved word.
Make reserved words are:
* `accountName`: name of the connection used by the app module,
* `teamID`: ID of the team to which the active user is currently assigned.
If you use a Make reserved word for the `name` key of a parameter, the value stored in the internal Make parameter will be used by your parameter too.
Consider the following configuration of a connection. The parameter labeled `Account Name` has the `name` key set to preserved word `accountName`.
{% tabs %}
{% tab title="Code example" %}
```json
[
{
"name": "apiKey",
"type": "password",
"label": "API Key",
"editable": true,
"required": true
},
{
"name": "accountName", // reserved word used here!
"type": "text",
"label": "Account name",
"editable": true,
"required": true
}
]
```
{% hint style="info" %}
The code above leads to mirroring the value from the default `Connection name` parameter into a parameter labeled `Account name`. The value `accountName` is set by Make to the name of the created connection.
{% endhint %}
{% endtab %}
{% tab title="Duplication of the connection name value" %}
{% endtab %}
{% endtabs %}
---
# 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://developers.make.com/custom-apps-documentation/app-components/connections.md?ask=&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.
