---
title: "Rebill a managed subscription"
method: POST
path: "/subscriptions/charge"
tags: ["Subscriptions"]
---

# Rebill a managed subscription

`POST /subscriptions/charge`

Charges a customer for their [managed subscription](https://developer.fastspring.com/docs/managed-subscriptions-and-usage-based-billing).

This API processes charges immediately and sends notifications to the customer. It is used for managed subscriptions that rely on seller actions for charges, reminders, and deactivation, with no internal subscription date tracking.

For large rebill volumes (e.g., January 1st annual renewals), we recommend to divide workloads into batches and call the endpoint sequentially, waiting for each batch to complete.Partial failures in a batch are detailed in the response for each subscription.

## Request body

- ChargeSubscriptionRequest — Request schema for charging a subscription.
  - `subscriptions` object[], required — List of subscriptions to charge.
    - `subscription` string, required — Unique identifier of the subscription to charge. We recommended a max of 50 subscription IDs in a request body batch.

## Response `200`

OK

- ChargeSubscriptionResponse — Response schema for a successful subscription charge.
  - `subscription` object[]
    - `subscription` string — Identifier of the charged subscription.
    - `action` string — Action performed (e.g., subscription.charge).
    - `result` string — Result of the charge operation.

## Other responses

- `400` — Bad Request
- `401` — Authentication credentials are missing or invalid.
- `429` — Rate limit exceeded. Retry after the number of seconds specified in the Retry-After header.
- `500` — Internal server error.

---

[API](https://skmtc.net/fastspring/apis/fastspring-api-accounts.md) · [All operations](https://skmtc.net/fastspring/apis/fastspring-api-accounts/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fastspring/fastspring-api-accounts/versions/ae2f0b97db3e/schema)