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

# Sign Agreement Documents

POST https://live.tradovateapi.com/v1/customerApplication/signagreementdocuments
Content-Type: application/json

### Sign the agreement documents for a customer application.

**Available to:** All authenticated users

**Environments:** Live

**[Rate Limit](/overview/core-concepts/rate-limits):** 10 requests per hour, 30-second back-off, counts all requests

Record the applicant's signature on the agreement documents prepared for a customer application. Call this after generating the documents with [`prepareAgreementDocuments`](/api/rest-api-endpoints/users/prepare-agreement-documents).

All fields are required:

- `customerApplicationId` — the application being signed, from [`startCustomerApplication`](/api/rest-api-endpoints/users/start-customer-application)
- `agreementIds` — the `AgreementDocument` entity IDs to sign; list them with [`agreementDocumentDependents`](/api/rest-api-endpoints/users/agreement-document-dependents)
- `agreementReadConfirmation` — must be `true`, confirming the applicant read the agreements
- `signature` — must match the applicant's full name exactly
- `date` — must be today's date (Central Time)

For individual, joint, and IRA applications, the signature is validated against the applicant's first and last name; on joint applications, a co-applicant login signs with the joint applicant's name. For entity applications, the signature must match the full name of the primary contact.

A successful response returns a `successHashCode`.

**Common Failure Scenarios**

- `customerApplicationId` or any of the `agreementIds` does not reference an existing entity.
- The application has no applicant details — submit them with [`submitApplicant`](/api/rest-api-endpoints/users/submit-applicant) and prepare the documents before signing.
- The signature does not match the applicant's full name, or the date is not today's date.
- The caller belongs to a reliance-agreement organization and cannot sign on behalf of customers.

**Error Messages**

| `errorText` | Trigger |
|-------------|---------|
| `"No applicant details"` | The application has no applicant record to validate the signature against. |
| `"Invalid date"` | `date` cannot be parsed as a date. |
| `"Signature date should be today’s date. Please update the date and click Sign."` | `date` is not today's date in Central Time. |
| `"Signature should be the same as full name of the applicant"` | `signature` does not match the applicant's full name. |
| `"Signature should be the same as full name of the primary contact"` | On an entity application, `signature` does not match the primary contact's full name. |
| `"This operation should be performed by your organization"` | The caller's organization has a reliance agreement, and the caller cannot sign on behalf of customers. |

Reference: https://partner.ninjatrader.com/connect/api/rest-api-endpoints/users/sign-agreement-documents

## OpenAPI Specification

```yaml
openapi: 3.1.0
info:
  title: connect
  version: 1.0.0
paths:
  /customerApplication/signagreementdocuments:
    post:
      operationId: sign-agreement-documents
      summary: Sign Agreement Documents
      description: >-
        ### Sign the agreement documents for a customer application.


        **Available to:** All authenticated users


        **Environments:** Live


        **[Rate Limit](/overview/core-concepts/rate-limits):** 10 requests per
        hour, 30-second back-off, counts all requests


        Record the applicant's signature on the agreement documents prepared for
        a customer application. Call this after generating the documents with
        [`prepareAgreementDocuments`](/api/rest-api-endpoints/users/prepare-agreement-documents).


        All fields are required:


        - `customerApplicationId` — the application being signed, from
        [`startCustomerApplication`](/api/rest-api-endpoints/users/start-customer-application)

        - `agreementIds` — the `AgreementDocument` entity IDs to sign; list them
        with
        [`agreementDocumentDependents`](/api/rest-api-endpoints/users/agreement-document-dependents)

        - `agreementReadConfirmation` — must be `true`, confirming the applicant
        read the agreements

        - `signature` — must match the applicant's full name exactly

        - `date` — must be today's date (Central Time)


        For individual, joint, and IRA applications, the signature is validated
        against the applicant's first and last name; on joint applications, a
        co-applicant login signs with the joint applicant's name. For entity
        applications, the signature must match the full name of the primary
        contact.


        A successful response returns a `successHashCode`.


        **Common Failure Scenarios**


        - `customerApplicationId` or any of the `agreementIds` does not
        reference an existing entity.

        - The application has no applicant details — submit them with
        [`submitApplicant`](/api/rest-api-endpoints/users/submit-applicant) and
        prepare the documents before signing.

        - The signature does not match the applicant's full name, or the date is
        not today's date.

        - The caller belongs to a reliance-agreement organization and cannot
        sign on behalf of customers.


        **Error Messages**


        | `errorText` | Trigger |

        |-------------|---------|

        | `"No applicant details"` | The application has no applicant record to
        validate the signature against. |

        | `"Invalid date"` | `date` cannot be parsed as a date. |

        | `"Signature date should be today’s date. Please update the date and
        click Sign."` | `date` is not today's date in Central Time. |

        | `"Signature should be the same as full name of the applicant"` |
        `signature` does not match the applicant's full name. |

        | `"Signature should be the same as full name of the primary contact"` |
        On an entity application, `signature` does not match the primary
        contact's full name. |

        | `"This operation should be performed by your organization"` | The
        caller's organization has a reliance agreement, and the caller cannot
        sign on behalf of customers. |
      tags:
        - Users
      parameters:
        - name: Authorization
          in: header
          description: Bearer authentication
          required: true
          schema:
            type: string
      responses:
        '200':
          description: AgreementDocumentsResponse
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AgreementDocumentsResponse'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SignAgreementDocuments'
servers:
  - url: https://live.tradovateapi.com/v1
    description: https://live.tradovateapi.com/v1
components:
  schemas:
    SignAgreementDocuments:
      type: object
      properties:
        customerApplicationId:
          type: integer
          format: int64
        agreementReadConfirmation:
          type: boolean
        signature:
          type: string
        date:
          type: string
        agreementIds:
          type: array
          items:
            type: integer
            format: int64
      required:
        - customerApplicationId
        - agreementReadConfirmation
        - signature
        - date
        - agreementIds
      title: SignAgreementDocuments
    AgreementDocumentsResponse:
      type: object
      properties:
        errorText:
          type: string
          description: Non-empty if the request failed
        successHashCode:
          type: integer
          format: int64
      title: AgreementDocumentsResponse
  securitySchemes:
    bearer_access_token:
      type: http
      scheme: bearer

```

## Examples



**Request**

```json
{
  "customerApplicationId": 123456789,
  "agreementReadConfirmation": true,
  "signature": "John A. Smith",
  "date": "2024-06-10",
  "agreementIds": [
    987654321,
    987654322
  ]
}
```

**Response**

```json
{
  "errorText": "",
  "successHashCode": 452198765
}
```

**SDK Code**

```python
import requests

url = "https://live.tradovateapi.com/v1/customerApplication/signagreementdocuments"

payload = {
    "customerApplicationId": 123456789,
    "agreementReadConfirmation": True,
    "signature": "John A. Smith",
    "date": "2024-06-10",
    "agreementIds": [987654321, 987654322]
}
headers = {
    "Authorization": "Bearer <token>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.json())
```

```javascript
const url = 'https://live.tradovateapi.com/v1/customerApplication/signagreementdocuments';
const options = {
  method: 'POST',
  headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
  body: '{"customerApplicationId":123456789,"agreementReadConfirmation":true,"signature":"John A. Smith","date":"2024-06-10","agreementIds":[987654321,987654322]}'
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}
```

```go
package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "https://live.tradovateapi.com/v1/customerApplication/signagreementdocuments"

	payload := strings.NewReader("{\n  \"customerApplicationId\": 123456789,\n  \"agreementReadConfirmation\": true,\n  \"signature\": \"John A. Smith\",\n  \"date\": \"2024-06-10\",\n  \"agreementIds\": [\n    987654321,\n    987654322\n  ]\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("Authorization", "Bearer <token>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(res)
	fmt.Println(string(body))

}
```

```ruby
require 'uri'
require 'net/http'

url = URI("https://live.tradovateapi.com/v1/customerApplication/signagreementdocuments")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "{\n  \"customerApplicationId\": 123456789,\n  \"agreementReadConfirmation\": true,\n  \"signature\": \"John A. Smith\",\n  \"date\": \"2024-06-10\",\n  \"agreementIds\": [\n    987654321,\n    987654322\n  ]\n}"

response = http.request(request)
puts response.read_body
```

```java
import com.mashape.unirest.http.HttpResponse;
import com.mashape.unirest.http.Unirest;

HttpResponse<String> response = Unirest.post("https://live.tradovateapi.com/v1/customerApplication/signagreementdocuments")
  .header("Authorization", "Bearer <token>")
  .header("Content-Type", "application/json")
  .body("{\n  \"customerApplicationId\": 123456789,\n  \"agreementReadConfirmation\": true,\n  \"signature\": \"John A. Smith\",\n  \"date\": \"2024-06-10\",\n  \"agreementIds\": [\n    987654321,\n    987654322\n  ]\n}")
  .asString();
```

```php
<?php
require_once('vendor/autoload.php');

$client = new \GuzzleHttp\Client();

$response = $client->request('POST', 'https://live.tradovateapi.com/v1/customerApplication/signagreementdocuments', [
  'body' => '{
  "customerApplicationId": 123456789,
  "agreementReadConfirmation": true,
  "signature": "John A. Smith",
  "date": "2024-06-10",
  "agreementIds": [
    987654321,
    987654322
  ]
}',
  'headers' => [
    'Authorization' => 'Bearer <token>',
    'Content-Type' => 'application/json',
  ],
]);

echo $response->getBody();
```

```csharp
using RestSharp;

var client = new RestClient("https://live.tradovateapi.com/v1/customerApplication/signagreementdocuments");
var request = new RestRequest(Method.POST);
request.AddHeader("Authorization", "Bearer <token>");
request.AddHeader("Content-Type", "application/json");
request.AddParameter("application/json", "{\n  \"customerApplicationId\": 123456789,\n  \"agreementReadConfirmation\": true,\n  \"signature\": \"John A. Smith\",\n  \"date\": \"2024-06-10\",\n  \"agreementIds\": [\n    987654321,\n    987654322\n  ]\n}", ParameterType.RequestBody);
IRestResponse response = client.Execute(request);
```

```swift
import Foundation

let headers = [
  "Authorization": "Bearer <token>",
  "Content-Type": "application/json"
]
let parameters = [
  "customerApplicationId": 123456789,
  "agreementReadConfirmation": true,
  "signature": "John A. Smith",
  "date": "2024-06-10",
  "agreementIds": [987654321, 987654322]
] as [String : Any]

let postData = JSONSerialization.data(withJSONObject: parameters, options: [])

let request = NSMutableURLRequest(url: NSURL(string: "https://live.tradovateapi.com/v1/customerApplication/signagreementdocuments")! as URL,
                                        cachePolicy: .useProtocolCachePolicy,
                                    timeoutInterval: 10.0)
request.httpMethod = "POST"
request.allHTTPHeaderFields = headers
request.httpBody = postData as Data

let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
  if (error != nil) {
    print(error as Any)
  } else {
    let httpResponse = response as? HTTPURLResponse
    print(httpResponse)
  }
})

dataTask.resume()
```