---
title: "Encode and sign object"
method: POST
path: "/v2/tools/encode-and-sign"
tags: ["Tools/Encoding"]
---

# Encode and sign object

`POST /v2/tools/encode-and-sign`

Encodes and signs any JSON object. The encoded value includes a signature
tied to the authenticated user's ID, which can later be verified using the
decode-and-verify endpoint.

**Important**: The request must specify the `Content-Type: application/json`
HTTP header.

## Request body

- object

## Response `200`

- EncodeAndSignResponse
  - `data` EncodeAndSignData, required
    - `encoded` string, required

## Other responses

- `400` — Bad request - invalid input parameters or request body.
- `401` — Unauthorized - authentication required or invalid token.
- `403` — Forbidden - insufficient permissions to perform this action.
- `405` — Method not allowed.
- `413` — Payload too large - the request body exceeds the size limit.
- `415` — Unsupported media type - the Content-Encoding of the request is not supported.
- `429` — Too many requests - rate limit exceeded.

---

[API](https://skmtc.net/apify/apis/apify-api.md) · [All operations](https://skmtc.net/apify/apis/apify-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/apify/apify-api/versions/01a71794279b/schema)