**Source URL:** https://general.veevavault.dev/clinical/vault-api/api-reference/26.1/binders/binder-sections/create-binder-section.md

# Create Binder Section



Create a new section in a binder.

Binders cannot exceed 50,000 nodes. Nodes include documents, sections, and component binders. If a binder has reached its limit, binder nodes cannot be added to the binder or any of its component binders, even if the component binders have not reached the 50,000 node limit.

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

## Headers {#headers}

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

## URI Path Parameters {#uri-path-parameters}

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

## Body Parameters {#body-parameters}

<FieldTable>
| Field Name | Description |
| --- | --- |
| `name__v` | Specify a name for the new section. |
| `section_number__v` | Enter a numerical value for the new section. |
| `parent_id__v` | 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` | 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 {#request}

<CodeExample title="">
```
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 {#response}

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

```
</CodeExample>

## Response Details {#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](/clinical/vault-api/api-reference/26.1/binders/binder-sections/retrieve-binder-version-section)  
**Next:** [Update Binder Section](/clinical/vault-api/api-reference/26.1/binders/binder-sections/update-binder-section)