# Create a line item Stripe quantity

> POST /api/customers/{id}/contracts/{contractId}/line-items/{itemId}/stripe-quantity on the Vigilbase One API.

Source: https://docs.vigilbase.com/one/api/reference/customers/post-customers-id-contracts-contract-id-line-items-item-id-stripe-quantity

`POST https://one.vigilbase.com/api/customers/{id}/contracts/{contractId}/line-items/{itemId}/stripe-quantity`

## Authorizations

Send one of these:

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`.
- `Authorization` (string, header, required): Organisation API key (`vb_one_…`) from **Settings → API keys** in Vigilbase One, sent as `Authorization: Bearer vb_one_…`. Needs a key with write access: read-only keys get `403` with the code `read_only_key`. See [organisation API keys](https://docs.vigilbase.com/one/api#organisation-api-keys).
- Permissions checked: `manage:stripe`, `write:contracts`

## Path parameters

- `id` (string, required)
- `contractId` (string, required)
- `itemId` (string, required)

## Body (application/json)

- `quantity` (integer, required): Maximum 100000.
- `expectedQuantity` (integer, required): Minimum 0, maximum 9007199254740991.

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`, or a write API key (vb_one_…)
curl --request POST \
  --url 'https://one.vigilbase.com/api/customers/{id}/contracts/{contractId}/line-items/{itemId}/stripe-quantity' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"quantity":123,"expectedQuantity":123}'
```