> For the complete documentation index, see [llms.txt](https://rwaperp-1.gitbook.io/rwaperp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwaperp-1.gitbook.io/rwaperp-docs/rwa-perp-b2b-api/rest-api-reference/funds-and-settlement/post-v1-delegate-orderly-key.md).

# post v1 delegate orderly key

`POST /v1/delegate_orderly_key`

**Authentication:** Wallet

**Rate limit:** 1 requests per second

## Description

Adds an API key for a delegate signer after the delegate relationship has been authorized.

## Parameters

No fields are defined in the published schema.

## Request body

| Field                      | Type    | Required | Description                                                                                                                      |
| -------------------------- | ------- | -------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `message`                  | object  | Yes      | Message object containing the message that is signed by the wallet owner                                                         |
| `message.delegateContract` | string  | Yes      | Delegate contract address authorized to act for the account.                                                                     |
| `message.brokerId`         | string  | Yes      | Builder ID                                                                                                                       |
| `message.chainId`          | integer | Yes      | Chain ID of registering chain (within those that are supported by the Network)                                                   |
| `message.orderlyKey`       | string  | Yes      | API key to be added                                                                                                              |
| `message.scope`            | string  | Yes      | Valid scopes are `read`, `trading`, and `asset`. Multiple scopes can be sent as a comma-separated string such as `read,trading`. |
| `message.timestamp`        | number  | Yes      | timestamp in UNIX milliseconds                                                                                                   |
| `message.expiration`       | number  | Yes      | Expiration time of the key in UNIX milliseconds. The maximum allowed expiration is 365 days from creation.                       |
| `signature`                | string  | Yes      | Signature generated by signing the message object.                                                                               |
| `userAddress`              | string  | Yes      | Address of the wallet that signed the message object.                                                                            |

## Responses

### HTTP 200

OK

| Field              | Type    | Required | Description                                                                                   |
| ------------------ | ------- | -------- | --------------------------------------------------------------------------------------------- |
| `success`          | boolean | Yes      | Indicates whether the request was successful. Example: `True`                                 |
| `timestamp`        | integer | No       | Server timestamp in milliseconds. Example: `1702989203989`                                    |
| `data`             | object  | Yes      | —                                                                                             |
| `data.id`          | integer | No       | Internal ID of the created API key record. Example: `123`                                     |
| `data.orderly_key` | string  | Yes      | API key added to the account. Example: `ed25519:FRXntsPJBCy6dzKv9WPw4eYSw3rKU9Npz3T6UmvvJc9Z` |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://rwaperp-1.gitbook.io/rwaperp-docs/rwa-perp-b2b-api/rest-api-reference/funds-and-settlement/post-v1-delegate-orderly-key.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.