> For the complete documentation index, see [llms.txt](https://developer.securecontainerrelease.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.securecontainerrelease.com/getting-started/testing-and-sandbox/creating-a-jwt-testing-token-manually..md).

# Creating a JWT testing token manually.

You can generate a testing token at [jwt.io](https://jwt.io) with your settings and secret, and use Postman for testing it.

<figure><img src="https://3962621206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F42KNM6Ikou97oywFeUuW%2Fuploads%2F6jaTKhBpf8fMoH3KjCIb%2Fimage.png?alt=media&amp;token=2b00193a-4d05-4d9c-add8-ebbb42cd0606" alt=""><figcaption></figcaption></figure>

In the JWT payload, only the `iat` (issued at) and `exp` (expiration time) fields are required.

{% code title="Example: Token expires Sep 2024" %}

```json
{
  "iat": 1694080518,
  "exp": 1725702918
}
```

{% endcode %}

In the payload, the expiration date is **key** and should be specified as an **integer** (an epoch). There are no other fields required, so the `“issued at”` and `“expiration time”`-fields are sufficient.