---
title: "GET /wiki-pages/{page_uuid}/signature-requests/{request_uuid}/document/export"
method: GET
path: "/wiki-pages/{page_uuid}/signature-requests/{request_uuid}/document/export"
tags: ["Wiki Pages"]
---

# GET /wiki-pages/{page_uuid}/signature-requests/{request_uuid}/document/export

`GET /wiki-pages/{page_uuid}/signature-requests/{request_uuid}/document/export`

## Request

- Base URL: `https://api.laver.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.laver.app/wiki-pages/{page_uuid}/signature-requests/{request_uuid}/document/export`
- Auth: one of:
  - HTTP bearer
  - API key in header `Authorization`

## Path parameters

- `page_uuid` string, uuid, required
- `request_uuid` string, uuid, required

## Response `2XX`

Success. This endpoint declares no response schema, so its body is not part of the generated contract.

## Other responses

- `400`: The request failed schema validation, or the handler rejected its contents. Undeclared properties are rejected on every body, path and query schema, so an unexpected field is a 400 rather than a silently ignored one.
- `401`: No credential, or one that is expired, revoked or not accepted by this endpoint.
- `404`: No such resource — or one the caller may not see. Membership and board access are enforced by answering 404 rather than 403, so a stranger never learns that a resource exists.
- `423`: The workspace is suspended, which is an action taken by Laver rather than a billing state. Reads are refused alongside writes, and no plan change lifts it — unlike a 402, which the workspace can settle itself.
- `429`: The rate limit was exceeded. The budget is keyed on the authenticated session user or API key, falling back to the caller IP.

---

[API](https://skmtc.dev/laver/apis/laver-api.md) · [All operations](https://skmtc.dev/laver/apis/laver-api/llms.txt) · [OpenAPI document](https://skmtc.dev/laver/apis/laver-api/revisions/91e3db25a19c?raw)