Delete a subaccount by ID

Paymish Docs

Paymish
Subaccounts

Endpoint Overview

DELETE /api/transaction-service/external/v1/subaccounts/{id} Requires authentication

Purpose

Use this endpoint to delete a subaccount by id. It belongs to the Subaccounts collection and is designed for backend integrations.

Request shape

1 parameter and 0 documented body fields using application/json.

Implementation Guide

Recommended workflow

Authenticate first and inject a valid bearer token or secret key before calling the endpoint.

Validate the input data, identifiers, and account state in your application before making the request.

Send the DELETE request from your backend using the required headers and the expected content type (application/json).

Persist the important identifiers returned in the response so later lookups, webhooks, or support actions can be linked correctly.

Implementation notes

Construct path parameters carefully and avoid string concatenation mistakes when building the final URL.
Protect state-changing operations with strong validation, logging, and retry rules to avoid duplicate mutations.

Path Parameters

id required

integer

Unique identifier of the subaccount to be deleted.

Responses

200 Subaccount deleted successfully.

404 Subaccount not found.

500 Internal server error.

Expected Outcomes

Subaccount deleted successfully.

{
  "message": "Subaccount deleted"
}

Subaccount not found.

{
  "message": "Subaccount not found",
  "code": 404,
  "error": "value"
}

After the response:

Log the Paymish reference or request context returned by the API so support teams can trace the call later.
Retry only when the failure is safe to repeat; otherwise correct the payload or auth state first.
Store enough internal metadata to match the API response back to your order, payout, case, or checkout record.

Language Notes

Python

Use `requests` from a backend worker, service, or Django/Flask app and centralize headers in a reusable helper.

Node.js

Use `axios` or `fetch` from Node.js services only; do not place secret credentials in frontend bundles.

PHP

Wrap cURL usage in a small client class so auth headers, error handling, and logging stay consistent.

cURL

Use cURL for smoke testing and debugging, then move the final logic into your backend service code.

Code Examples

import requests

headers = {
    "Authorization": "Bearer YOUR_SECRET_KEY",
}
response = requests.delete(
    "https://api.paymish.com/api/transaction-service/external/v1/subaccounts/{id}",
    headers=headers,
)

data = response.json()
print(data)

const axios = require("axios");

const response = await axios({
  method: "delete",
  url: "https://api.paymish.com/api/transaction-service/external/v1/subaccounts/{id}",
  headers: {
    Authorization: "Bearer YOUR_SECRET_KEY",
  }
});

console.log(response.data);

curl https://api.paymish.com/api/transaction-service/external/v1/subaccounts/{id} \
  -X DELETE \
  -H "Authorization: Bearer YOUR_SECRET_KEY"

<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://api.paymish.com/api/transaction-service/external/v1/subaccounts/{id}");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "DELETE");
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    "Authorization: Bearer YOUR_SECRET_KEY",
]);

$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);

Previous endpoint Update a subaccount by ID Next endpoint Get document.