> This page is for RakeSign.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.cloudraker.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server.

# RakeSign API

The RakeSign API uses this base URL:

```text
https://api.cloudraker.com/v1/signing
```

Use it to prepare documents, manage templates, send signature requests, and track results.
The API also exposes contacts, signing groups, branding, forms, bulk jobs, reports, and standing delegation.

## Start an integration

1. Ask an organization administrator to create a scoped key in **RakeSign → Developers**.
2. Choose the team whose shared resources the integration needs.
3. Follow the [document workflow](/rakesign/developers/documents).
4. Subscribe to [webhooks](/rakesign/developers/webhooks) to track delivery and signing events.

Send the key as a bearer credential from your server:

```bash
curl 'https://api.cloudraker.com/v1/signing/documents?pageSize=50' \
  -H "Authorization: Bearer $RAKESIGN_API_KEY"
```

Document lists return `items` and `nextCursor`.
Send the returned cursor with your next list request.
Individual resource operations return the resource directly.

## One product surface

API documents appear in RakeSign under the integration's team.
The app and API use the same versioned drafts, templates, access rules, signature engine, and audit records.

An integration has a stable identity separate from its credential.
Rotating a key preserves document ownership and scheduled work references.
Permission changes, expiry, and revocation apply when requests or scheduled work run.

## Errors and retries

Errors use the `/v1` error envelope with `code`, `message`, `retryable`, and `requestId`.
Branch on HTTP status and code.
Do not parse the human-readable message.

| Status         | Action                                                                     |
| -------------- | -------------------------------------------------------------------------- |
| `400` or `422` | Correct the request or unsupported signing configuration.                  |
| `401`          | Check the bearer credential.                                               |
| `403`          | Check permissions, team management, expiry, or revocation.                 |
| `404`          | Check the ID and access. Inaccessible resources also return this status.   |
| `409`          | Refresh the resource and resolve its version or state conflict.            |
| `429`          | Wait for `Retry-After` before retrying.                                    |
| `503`          | Retry with backoff after checking whether the operation already completed. |

The API shares the organization's `/v1` request budget.
See [rate limits](/paperwork/developers/rate-limits) for the response headers and backoff guidance.

Use documented idempotency and version controls for each operation.
Do not assume every mutation supports `Idempotency-Key`.

## Existing Paperwork integrations

`POST /v1/sign` remains available with its existing request and run response contract.
Use [the migration guide](/rakesign/developers/migration) to move new work to RakeSign without changing existing runs.