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 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.

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.

Important: These parameters are essential for integrations involving the sending of credentials or binary files via multipart forms.