# Sign Message

Sign Message with your Private Key will generate a “hash” that can be verified with your public key.

Action available for the following operating systems:

![](/files/-MAlQBZuuTnc6hyzKSVQ)

### Parameters

* **Data Type** *\<numeric> -* Select the data type of your message
  * 1 - Text UTF-16 LE
  * 2 - Text ANSI/Binary
  * 3 - Text UTF-8
* **Source** *\<string> -* Select a Text, Variable or control to be Sign.
* **Target** *-* Select a Variable or Control.
* **Result Encoding** *\<numeric>*
  * 1 - None (Binary)
  * 2 - Base 64
* **Algorithm** *\<numeric> -* Select the algorithm to be used:
  * Dynamic
    * 1 - RSA PKCS1 Padding
    * 2 - RSA OAEP Padding
* **Key (Private)** *\<string>* - Fill with a String, Control or Variable. **PrivateKey** must be provided in PKCS#8 format encoded in Base64 (with no headers/footers).

{% hint style="info" %}
For more information see Android documentation: <https://developer.android.com/reference/java/security/spec/PKCS8EncodedKeySpec>
{% endhint %}

* **Key Size** *\<numeric> -* Default value: 2048


---

# 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://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-code-flow/sign-message.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.