# DeleteSubscriptionItemsItem

From **Stripe API**.

`DELETE /v1/subscription_items/{item}`

<p>Deletes an item from the subscription. Removing a subscription item from a subscription will not cancel the subscription.</p>

## Parameters

### `item`

- Location: path
- Required: true
- Type: `string`
- maxLength: `5000`

## Request body

- Required: false
### `application/x-www-form-urlencoded`

- Type: `object`

```json
{"additionalProperties":false,"properties":{"clear_usage":{"description":"Delete all usage for the given subscription item. Allowed only when the current plan's `usage_type` is `metered`.","type":"boolean"},"proration_behavior":{"description":"Determines how to handle [prorations](https://stripe.com/docs/subscriptions/billing-cycle#prorations) when the billing cycle changes (e.g., when switching plans, resetting `billing_cycle_anchor=now`, or starting a trial), or if an item's `quantity` changes. Valid values are `create_prorations`, `none`, or `always_invoice`.\n\nPassing `create_prorations` will cause proration invoice items to be created when applicable. These proration items will only be invoiced immediately under [certain conditions](https://stripe.com/docs/subscriptions/upgrading-downgrading#immediate-payment). In order to always invoice immediately for prorations, pass `always_invoice`.\n\nProrations can be disabled by passing `none`.","enum":["always_invoice","create_prorations","none"],"type":"string"},"proration_date":{"description":"If set, the proration will be calculated as though the subscription was updated at the given time. This can be used to apply the same proration that was previewed with the [upcoming invoice](https://stripe.com/docs/api#retrieve_customer_invoice) endpoint.","format":"unix-time","type":"integer"}},"type":"object"}
```

## Security

### `basicAuth`

- Type: `http`
- Request header: `Authorization`
- Scheme: `basic`
Send credentials in the `Authorization` request header using the `Basic` scheme.

Basic HTTP authentication. Allowed headers-- Authorization: Basic <api_key> | Authorization: Basic <base64 hash of `api_key:`>

### `bearerAuth`

- Type: `http`
- Request header: `Authorization`
- Scheme: `bearer`
- Bearer format: `auth-scheme`
Send the token in the `Authorization` request header using the `Bearer` scheme.

Bearer HTTP authentication. Allowed headers-- Authorization: Bearer <api_key>

## Responses

### `200`

Successful response.

### `application/json`

- Type: `object`

```json
{"properties":{"deleted":{"description":"Always true for a deleted object","enum":[true],"type":"boolean"},"id":{"description":"Unique identifier for the object.","maxLength":5000,"type":"string"},"object":{"description":"String representing the object's type. Objects of the same type share the same value.","enum":["subscription_item"],"type":"string"}},"required":["deleted","id","object"],"title":"DeletedSubscriptionItem","type":"object","x-expandableFields":[],"x-resourceId":"deleted_subscription_item"}
```

### `default`

Error response.

### `application/json`

- Type: `object`

An error response from the Stripe API

```json
{"description":"An error response from the Stripe API","properties":{"error":{"$ref":"#/components/schemas/api_errors"}},"required":["error"],"type":"object"}
```

## Request examples

### cURL

```shell
curl --request DELETE \
  --url https://api.stripe.com/v1/subscription_items/{item} \
  --header 'content-type: application/x-www-form-urlencoded' \
  --data '{
  "clear_usage": true,
  "proration_behavior": "string",
  "proration_date": 1
}'
```