**Source URL:** https://general.veevavault.dev/commercial/vault-api/api-reference/22.3/binders/binder-sections/create-binder-section

# Create Binder Section

Create a new section in a binder.

<Endpoint path="/api/{version}/objects/binders/{binder_id}/sections" method="POST" />

## Headers

<FieldTable>
| Name | Description |
| --- | --- |
| `Content-Type` | `application/x-www-form-urlencoded` |
| `Accept` | `application/json` (default) or `application/xml` |
</FieldTable>

## URI Path Parameters

<FieldTable>
| Name | Description |
| --- | --- |
| `{binder_id}` | The binder `id` field value. |
</FieldTable>

## Body Parameters

<FieldTable>
| Field Name | Description |
| --- | --- |
| `name__v`<Requiredness type="required" /> | Specify a name for the new section. |
| `section_number__v`<Requiredness type="optional" /> | Enter a numerical value for the new section. |
| `parent_id__v`<Requiredness type="optional" /> | If the new section is going to be a subsection, enter the Node ID of the parent section. If left blank, the new section will become a top-level section in the binder. When querying fields on binder nodes, this field corresponds to the `parent_section_id__sys` field. |
| `order__v`<Requiredness type="optional" /> | Enter a number reflecting the position of the section within the binder or parent section. A value of `1` has special behavior and instructs Vault to place the section at the first ordinal position of the binder, regardless of any existing `order__v` values. If provided with a negative value or omitted, Vault places the section at the last ordinal position of the binder, regardless of any existing `order__v` values. |
</FieldTable>

## Request

<CodeExample title="">
```bash
curl -X POST -H "Authorization: {SESSION_ID}" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "name__v=VeevaProm Additional Information" \
-d "section_number__v=1.3" \
-d "parent_id__v=1427232809771:1381853041" \
-d "order__v=1" \
https://myvault.veevavault.com/api/v15.0/objects/binders/566/sections
```
</CodeExample>

## Response

<CodeExample title="">
```json
{
    "responseStatus": "SUCCESS",
    "id": "1427486900128:1467568099"
}
```
</CodeExample>

## Response Details

On SUCCESS, Vault returns the Node ID of the newly created section. This is unique within the binder, regardless of level.

---

**Previous:** [Retrieve Binder Version Section](/commercial/vault-api/api-reference/22.3/binders/binder-sections/retrieve-binder-version-section)  
**Next:** [Update Binder Section](/commercial/vault-api/api-reference/22.3/binders/binder-sections/update-binder-section)