# Recover a YoPrint billing operation

```http
POST https://secure.yoprint.com/v1/api/store/{team_slug}/setting/subscription/operation/{operation_id}/recover
```

- API version: v1
- Operation ID: `v1_public_setting_subscription_operation_recover`
- Section: Team settings › [YoPrint subscription](https://developer.yoprint.com/reference/yoprint-subscription.md)
- Web page: https://developer.yoprint.com/reference/yoprint-subscription/v1-setting-subscription-operation-recover/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Finishes a billing operation whose `next_action` is `recover`: YoPrint reads Stripe and settles the operation to match. It never repeats a step Stripe already accepted, so it can't charge twice. Safe to call again. Returns the operation.

## Permission

The team owner, or a member with the Manage Billing permission. Manage Settings alone is not enough.

## Side effects

- Reads from Stripe and may complete the change the operation started.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.
- `operation_id` (string, required): The `operation_id` you chose when you started the change: 16 to 64 letters, digits, `_` or `-`. Not a hash id. Matches `^[A-Za-z0-9_-]{16,64}$`. Example `billing-checkout-01JZ000000000000`.

## Request body

This operation takes no request body.

### Example request

```bash
curl -X POST 'https://secure.yoprint.com/v1/api/store/your-team/setting/subscription/operation/billing-checkout-01JZ000000000000/recover' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` The billing operation reached a successful terminal state.

Fields:

- `data` (object, required)
  - `error_code` (string | null, required): Matches `^[a-z0-9_:-]{1,64}$`.
  - `kind` (string, required): One of: `"card_prepare"`, `"checkout_create"`, `"checkout_swap"`, `"payment_retry"`, `"subscription_cancel"`, `"subscription_resume"`.
  - `next_action` (string, required): One of: `"recover"`, `"refresh_billing"`, `"start_new_operation"`, `"update_card_then_retry"`, `"use_different_card"`, `"wait"`.
  - `operation_id` (string, required): Matches `^[A-Za-z0-9_-]{16,64}$`.
  - `outcome` (string | null, required): One of: `"succeeded"`, `"payment_failed"`, `"safe_failed"`.
  - `retry_class` (string | null, required): One of: `"safe"`, `"compensated"`, `"provider_retry"`, `"reconciliation_required"`.
  - `state` (string, required)
  - `terminal` (boolean, required)
- `status` (integer, optional)
- `success` (boolean, optional)

Example response:

```json
{
  "data": {
    "error_code": null,
    "kind": "checkout_create",
    "next_action": "refresh_billing",
    "operation_id": "billing-checkout-01JZ000000000000",
    "outcome": "succeeded",
    "retry_class": null,
    "state": "settled",
    "terminal": true
  }
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
- `402` The provider declined payment and the terminal operation records the outcome.
- `403` You are not allowed to do this. `api_access_not_in_plan`: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only `{"message": "Insufficient Permission"}`. Other refusals use the error envelope, with `unauthorized` or `user_is_not_authorized`.
  - When: You are not the owner and your role lacks Manage Billing. The body is `{"message": "Insufficient Permission"}`, without the error envelope. Fix: Use the owner's key, or that of a member with Manage Billing.
- `404` Not found. `page_not_found`: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. `code: null`, with a message that starts "No query results for": there is no record with that id.
  - When: No operation of your team has this id (`billing_operation_not_found`). `error.code` is null; `error.message` names the record type. Fix: Use the `operation_id` you sent.
- `409` A different billing operation owns the team lifecycle or frozen state changed.
  - When: Another billing operation is in progress (`billing_operation_conflict`). Fix: Wait and read the operation again.
- `422` Validation failed or a terminal safe failure was recorded.
- `503` Billing provider configuration or readback is temporarily unavailable.
  - When: Billing is temporarily unavailable (`billing_provider_unavailable`), or the result couldn't be confirmed (`billing_recovery_result_unknown`). Fix: Try again later; recover is safe to repeat.

## Notes

- Part of your YoPrint subscription: what your shop pays YoPrint, not your customers' payments.
- AI apps (MCP connections) can't call this operation: they get 403 `agent_operation_not_available`. Use a personal API key.

## Related

- [Get a YoPrint billing operation](https://developer.yoprint.com/reference/yoprint-subscription/v1-setting-subscription-operation-show.md): `GET /v1/api/store/{team_slug}/setting/subscription/operation/{operation_id}`