> For the complete documentation index, see [llms.txt](https://docs.onum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/encryption-encoding/jwt-decode.md).

# JWT decode

## Description

This operation is used to decode JSON Web Tokens (JWTs). JWTs are commonly used for authentication and data exchange in web applications, and they consist of three parts:

* **Header** - Encoded metadata about the token. 
* **Payload** - Encoded claims or data being transmitted. 
* **Signature** - A cryptographic signature to verify the token’s integrity. 

This operation helps decode and inspect the header and payload of a JWT without verifying the signature.

***

## Data types

These are the input/output expected data types for this operation:

### Input data

![](/files/PLlLS9WDthpZu0nbKCNG) - JWT string you want to decode.

### Output data

![](/files/FiO6hMIDNPuoHDSTAxHC) - Decoded JWT strings

***

## Example

Suppose you want to **decode** a series of events in the **Base64** encoding scheme:

1. In your Pipeline, open the required [Action](https://onum.gitbook.io/onum-docs/the-workspace/pipelines/actions) configuration and select the input **Field**.
2. In the **Operation** field, choose **JWT Decode**.
3. Give your **Output field** a name and click **Save**. The values in your input field will be decoded. 

For example, the following JWT:

```
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
```

will be decoded as:

```
{
    "sub": "1234567890",
    "name": "John Doe",
    "iat": 1516239022
}
```

{% hint style="info" %}
You can try out operations with specific values using the **Input** field above the operation. You can enter the value in the example above and check the result in the **Output** field.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/encryption-encoding/jwt-decode.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.