---
title: "Fulfill a signature request"
method: POST
path: "/warden.warden.v1beta2.Msg/FulfilSignRequest"
tags: ["Msg"]
---

# Fulfill a signature request

`POST /warden.warden.v1beta2.Msg/FulfilSignRequest`

## Request body

- object
  - `creator` string
  - `request_id` string, uint64
  - `status` 'SIGN_REQUEST_STATUS_UNSPECIFIED' | 'SIGN_REQUEST_STATUS_PENDING' | 'SIGN_REQUEST_STATUS_FULFILLED' | 'SIGN_REQUEST_STATUS_REJECTED' — SignRequestStatus indicates the status of a signature request. A request starts as "pending", waiting to be picked up. Then it can move to either "approved" or "rejected", depending on the decision of the keychain. - SIGN_REQUEST_STATUS_UNSPECIFIED: The request is missing the status field. - SIGN_REQUEST_STATUS_PENDING: The request is waiting to be fulfilled. This is the initial state of a request. - SIGN_REQUEST_STATUS_FULFILLED: The request was fulfilled. This is a final state for a request. - SIGN_REQUEST_STATUS_REJECTED: The request was rejected. This is a final state for a request.
  - `payload` object
    - `signed_data` string, byte
  - `reject_reason` string

## Response `200`

A successful response.

## Other responses

- `default` — An unexpected error response.

---

[API](https://skmtc.dev/wardenprotocol/apis/http-api-console.md) · [All operations](https://skmtc.dev/wardenprotocol/apis/http-api-console/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/wardenprotocol/http-api-console/revisions/44399dd0ab35/schema)