Recover a YoPrint billing operation
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/yoprint-subscription/v1-setting-subscription-operation-recover.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
POST/
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.
Side effects
- Reads from Stripe and may complete the change the operation started.
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
The
operation_idyou 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
- Matches
Request body
This operation takes no request body.
Response
200The billing operation reached a successful terminal state.
Child fields (8)
- Matches
^[a-z0-9_:-]{1,64}$
- Matches
- One of:
"card_prepare","checkout_create","checkout_swap","payment_retry","subscription_cancel","subscription_resume"
- One of:
- One of:
"recover","refresh_billing","start_new_operation","update_card_then_retry","use_different_card","wait"
- One of:
- Matches
^[A-Za-z0-9_-]{16,64}$
- Matches
- One of:
"succeeded","payment_failed","safe_failed"
- One of:
- One of:
"safe","compensated","provider_retry","reconciliation_required"
- One of:
statusintegersuccessboolean
Errors
401The API key is missing or wrong (
unauthenticated).402The provider declined payment and the terminal operation records the outcome.
403You 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, withunauthorizedoruser_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.
404Not 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.codeis null;error.messagenames the record type. - Fix
- Use the
operation_idyou sent.
409A 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.
422Validation failed or a terminal safe failure was recorded.
503Billing 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
- GETGet a YoPrint billing operation
/v1/ api/ store/ {team_slug}/ setting/ subscription/ operation/ {operation_id}
