API Reference/Subaccounts
POST

Block or unblock a subaccount

Block or unblock a subaccount. See the request, response and integration notes.

POST/v1/subaccounts/{subaccountId}/blocked
https://integrate.api.kyvopay.com.br
cURL
curl -X POST https://integrate.api.kyvopay.com.br/v1/subaccounts/{subaccountId}/blocked \
  -H "X-API-Key: ky_XXXXX-XXXXX-XXXXX" \
  -H "Content-Type: application/json" \
  -d '{
  "is_blocked": false
}'
Resposta200 OK
{
  "data": {
    "daily_limit_centavos": "4990",
    "document": "12345678909",
    "email": "cliente@example.com",
    "external_reference": "pedido-12345",
    "id": "01HZ8K3M5N",
    "is_blocked": false,
    "monthly_limit_centavos": "4990",
    "name": "Cliente Exemplo",
    "public_id": "01HZ8K3M5N"
  },
  "error": {
    "code": "string",
    "details": {},
    "message": "string"
  },
  "request_id": "req_01HZ8K3M5N"
}

Authentication

X-API-Keystring · headerrequired

Use the ky_... key created under Integrations → API Keys in the KyvoPay dashboard.

Use this endpoint to block or unblock a subaccount. For safe retries, reuse the same idempotency key for the same business operation.

Request

Note

Private endpoints require the X-API-Key header. Keep credentials on your backend and log the response request_id for diagnostics.

Response

Implementation notes

  • Validate required input before sending the request.
  • Store returned public identifiers without assuming their format.
  • Treat 4xx validation errors as non-retryable until the request is corrected.
  • Retry timeouts, 429 and temporary 5xx responses with exponential backoff.
  • Keep the idempotency key stable across retries.
Need help? Contact support
© 2026 KyvoPay