# PayOut — Add sender

```
POST /Payouts/AddPayOutSender
```

Creates a sender record. **Call once per legal entity**, then reuse the returned `senderID`.

## Request body

| Field               | Type                        | Required | Description                         |
| ------------------- | --------------------------- | -------- | ----------------------------------- |
| `firstName`         | string                      | yes      | Sender's first name.                |
| `lastName`          | string                      | yes      | Sender's last name.                 |
| `dateOfBirth`       | string (ISO 8601)           | yes      | e.g., `1998-01-01T00:00:00Z`.       |
| `countryOfBirth`    | string (ISO 3166-1 alpha-2) | yes      | e.g., `CM`.                         |
| `address1`          | string                      | yes      | Street address.                     |
| `city`              | string                      | yes      | City.                               |
| `postalCode`        | string                      | **yes**  | Postal code (see warning below).    |
| `province`          | string                      | yes      | State/province/region.              |
| `country`           | string (ISO 3166-1 alpha-2) | yes      | Country of residence.               |
| `mobileCountryCode` | integer                     | yes      | Numeric dialing code.               |
| `mobileNumber`      | string                      | yes      | Mobile number without country code. |
| `emailAddress`      | string                      | yes      | Sender's email.                     |

{% hint style="warning" %}
**`postalCode` is required** despite being absent from some Swagger examples. For Cameroon, `00237` is an accepted default.
{% endhint %}

## Response

| Field      | Type          | Description                                            |
| ---------- | ------------- | ------------------------------------------------------ |
| `senderID` | string (UUID) | Store this and reuse for all payouts from this sender. |

## Example

```bash
curl -X POST "https://api-sandbox.nexterpay.io/Payouts/AddPayOutSender" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "firstName": "Habib",
    "lastName": "Ajao",
    "dateOfBirth": "1998-01-01T00:00:00Z",
    "countryOfBirth": "CM",
    "address1": "123 Street",
    "city": "Douala",
    "postalCode": "00237",
    "province": "Littoral",
    "country": "CM",
    "mobileCountryCode": 237,
    "mobileNumber": "670000000",
    "emailAddress": "test@email.com"
  }'
```

```json
{
  "senderID": "7f3e2a1b-9c8d-4e5f-a0b1-c2d3e4f5a6b7",
  "firstName": "Habib",
  "lastName": "Ajao",
  "country": "CM"
}
```


---

# Agent Instructions: 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:

```
GET https://docs.nexterpay.io/api-reference/payout-create-sender.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.