> ## Documentation Index
> Fetch the complete documentation index at: https://docs.portalhq.io/llms.txt
> Use this file to discover all available pages before exploring further.

# List active presignatures

> Lists active presignatures for the authenticated client. The response
includes both client-stored and Portal-managed presignatures. Use the
`managed` field on each entry to determine whether signing requires the
opaque `presignature` data blob or the `presignatureId`.




## OpenAPI

````yaml /openapi/enclave-mpc-api.yaml get /v1/presignatures
openapi: 3.1.0
info:
  title: Portal Enclave MPC API
  version: '1.0'
  description: |
    The Enclave MPC API provides endpoints for MPC wallet generation, signing,
    backup, and recovery. All endpoints require a Client API Key or Client
    Session Token as a Bearer token.

    ## Base URL
    `https://mpc-client.portalhq.io`
servers:
  - url: https://mpc-client.portalhq.io
security:
  - bearerAuth: []
tags:
  - name: MPC Operations
    description: MPC wallet generation, signing, asset transfers, backup, and recovery
paths:
  /v1/presignatures:
    get:
      tags:
        - MPC Operations
      summary: List active presignatures
      description: |
        Lists active presignatures for the authenticated client. The response
        includes both client-stored and Portal-managed presignatures. Use the
        `managed` field on each entry to determine whether signing requires the
        opaque `presignature` data blob or the `presignatureId`.
      operationId: listPresignatures
      responses:
        '200':
          description: Active presignatures returned successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListPresignaturesResponse'
              example:
                presignatures:
                  - id: <UUID>
                    expiresAt: '2025-03-18T10:00:00Z'
                    curve: SECP256K1
                    managed: true
        '401':
          description: Unauthorized
          content:
            text/plain:
              schema:
                type: string
              example: Incorrect API key format
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MpcErrorResponse'
components:
  schemas:
    ListPresignaturesResponse:
      type: object
      description: Active presignatures for the authenticated client.
      properties:
        presignatures:
          type: array
          items:
            $ref: '#/components/schemas/PresignatureEntry'
      required:
        - presignatures
    MpcErrorResponse:
      type: object
      description: Standard error response from the Enclave MPC API.
      properties:
        id:
          type: string
          description: >-
            Short error identifier (e.g. `DKG_FAILED`, `BAD_REQUEST`,
            `RPC_OP_FAILED`).
        message:
          type: string
          description: Human-readable error details.
      required:
        - id
    PresignatureEntry:
      type: object
      description: A listed active presignature.
      properties:
        id:
          type: string
          description: Unique identifier for the presignature.
        expiresAt:
          type: string
          format: date-time
          description: RFC 3339 expiration timestamp. May be omitted if unavailable.
        curve:
          type: string
          description: |
            The elliptic curve used by the presignature. Currently only
            `SECP256K1` is supported; `ED25519` will be added once support
            ships.
          enum:
            - SECP256K1
        managed:
          type: boolean
          description: |
            `true` if the presignature is Portal-managed (sign with
            `presignatureId`); `false` if it is client-stored (sign with the
            opaque `presignature` data blob).
      required:
        - id
        - curve
        - managed
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Client API Key or Client Session Token

````