> 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-settle-pnl.md).

# post v1 settle pnl

`POST /v1/settle_pnl`

**Authentication:** RWA

**Rate limit:** 1 requests per second

## Description

`verifyingContract` should use: `0x6F7a338F2aA472838dEFD3283eB360d4Dff5D203`.

## Parameters

No fields are defined in the published schema.

## Request body

| Field                 | Type    | Required | Description                                                                    |
| --------------------- | ------- | -------- | ------------------------------------------------------------------------------ |
| `signature`           | string  | Yes      | The signature generated by signing the message object via EIP-712              |
| `userAddress`         | string  | Yes      | The address of the wallet signing the message object via EIP-712               |
| `verifyingContract`   | string  | Yes      | Address of the ledger contract                                                 |
| `message`             | object  | Yes      | Message object containing the message that is signed by the wallet owner       |
| `message.brokerId`    | string  | Yes      | Builder ID                                                                     |
| `message.chainId`     | integer | Yes      | Chain ID of registering chain (within those that are supported by the Network) |
| `message.chainType`   | string  | No       | Chain type of the signing wallet. Supported values are `EVM` and `SOL`.        |
| `message.settleNonce` | integer | Yes      | Nonce returned by Get Settle PnL Nonce.                                        |
| `message.timestamp`   | integer | Yes      | current timestamp in UNIX milliseconds                                         |

## 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.settle_pnl_id` | integer | Yes      | Example: `1`                                                  |


---

# 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-settle-pnl.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.