---
title: "Submit data for processing"
method: POST
path: "/workers/{idOrName}/process"
---

# Submit data for processing

`POST /workers/{idOrName}/process`

Required role: set by AUTHTYPE in worker 

Submit data/document/file for processing such as for instance signing and get back the result (i.e. signature).

## Path parameters

- `idOrName` string, required

## Request body

- ProcessRequest — POJO that represents a process request.
  - `data` string, required — The input data to be processed (i.e. signed).
  - `encoding` 'NONE' | 'BASE64' — Choice of additional encoding of the data.
  - `metaData` object — Additional request metadata for the worker.

## Response `200`

The response data

- ProcessResponse — POJO that represents a process response.
  - `data` string — The resulting data (i.e the signature) in Base64 encoding
  - `requestId` string
  - `archiveId` string
  - `signerCertificate` string
  - `metaData` object

## Other responses

- `400` — Bad request from the client
- `403` — Access is forbidden!
- `404` — No such worker
- `500` — The server were unable to process the request. See server-side logs for more details.
- `503` — Crypto Token not available

---

[API](https://skmtc.dev/keyfactor/apis/signserver-rest-interface.md) · [All operations](https://skmtc.dev/keyfactor/apis/signserver-rest-interface/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/keyfactor/signserver-rest-interface/revisions/d1bc41f9bf6b/schema)