> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/how-to/how-to-force-data-types-in-multipart-requests.md).

# How to force data types in Multipart requests

In certain integration scenarios within **Skyone Studio**, the system may misidentify a parameter's format. For example, a plain text password might be interpreted as binary data and automatically converted to Base64. This behavior results in authentication failures or file corruption in the receiving API. The use of "force" commands ensures that the data is transmitted exactly in the expected format.

### Concept

There are two fundamental resources for type control in **Skyone Studio**:

* **Type Suffix (:-text):** Instructions attached to the parameter key that force the system to treat the value as pure text.
* **Force Parameter (\[STUDIO\_FORCE\_BASE64]):** Um prefixo utilizado no campo de valor que assegura o tratamento do dado especificamente como Base64.

### How to use

1. Create or edit a module up to the [Request](https://docs.skyone.cloud/english/skyone-studio/modules/settings-and-operations/module-settings.md) step.
2. In the field intended for the parameter name (Key), add the suffix: `-text` after the name.

   Example: In the key field, instead of just `password`, use `password:-text`
3. Configure the **Base64 Value**: For fields that strictly require the Base64 format, insert the prefix `[STUDIO_FORCE_BASE64]` before the variable or value.
4. Run a test to verify if the destination API receives the data in the correct format.

### Example

The table below illustrates the correct configuration as viewed in the platform's interface:

| **Parameter (Key)** | **Value**                           | **Purpose**                             |
| ------------------- | ----------------------------------- | --------------------------------------- |
| code:-text          | {{code}}                            | Forces the code to be sent as text.     |
| base64              | \[STUDIO\_FORCE\_BASE64] {{base64}} | Ensures conversion/treatment in Base64. |

{% hint style="danger" %}
Alert: Automatic Base64 detection by Skyone Studio is based on character patterns. If your text string matches these patterns, the conversion will mandatorily occur unless the `:-text` suffix is used.
{% endhint %}

{% hint style="warning" %}
Important: These parameters are essential for integrations involving the sending of credentials or binary files via multipart forms.
{% endhint %}


---

# 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.skyone.cloud/english/skyone-studio/how-to/how-to-force-data-types-in-multipart-requests.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.
