> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemreference/functions/security/aesdecrypt.md). # AesDecrypt {% hint style="info" %} The **`AesDecrypt()`** function decrypts a base64 encoded ciphertext to plaintext, using the given key and initialization vector. This function is NOT SQL compatible. For more information about SQL compatibility, see our [documentation](/platform/wemreference/sql-compatibility.md). {% endhint %} {% hint style="success" %} Returns a plaintext. \ Returns **`Unknown`** if one of the parameter values is unknown or outside the common valid boundaries. {% endhint %} ### Syntax

AesDecrypt(ciphertext, key, vector)

AesDecrypt(ciphertext, key, vector, encoding with BOM)

`ciphertext = "e3ieQNh8nKH/pHImo+JQmZvr+rhSGn4WHQJyTBmPCbA="`\ `key = "77616d666c51673763346e764b6c725242313668357a7a597131515a78303733"`\ `vector = "00000000000000000000000000000000"` `AesDecrypt(ciphertext, key, vector, false)`\ *=> "abcdefghijklmnopqrstuvwxyz"* `ciphertext BOM = "+8oDxXf+w91SR+/AkjpdcLSbygah8m3OQdapwnkAjvY="` `AesDecrypt(ciphertext, key, vector, true)`\ *=> "abcdefghijklmnopqrstuvwxyz"*

### Parameters

Name	Type	Required	Description	Required?
`ciphertext`	text	☑️	The input base64 encoded text which was encrypted you want to decrypt. It should be encrypted with the same key and vector values and using the AES algorithm.	yes
`key`	text	☑️	Text or data field that holds the encryption key. A key can be generated using AesKey()	yes
`vector`	text	☑️	Text or data field that holds the encryption vector. A proper Vector value can be generated using AesIv()
`encoding with BOM`	yes/no		enable or disable encoding with BOM.

--- # 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.wem.io/platform/wemreference/functions/security/aesdecrypt.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.