Delete methods — DELETE /v1/billing/portal/methods/{id}

Removes one card or account the caller has saved, at the address a hosted checkout reaches it by.

DELETE /v1/billing/portal/methods/{id}

Billing → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/billing/portal/methods/{id}`
Method	`DELETE`
Operation	`delete_billing_portal_methods_by_id`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Removes one card or account the caller has saved, at the address a hosted checkout reaches it by. One set of rows, two spellings: a card detached at either is gone from both, because there is one store behind them.

Request

1 field.

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the saved method to detach, from the path.

Response

Status	Body	Meaning
`200`	billing.Detachment	ok
`default`	problem-details	refused

200 body — 2 fields.

Field	In	Type	Always	Description
`deleted`	body	boolean	—	Deleted is whether the method was actually removed.
`id`	body	string	—	ID is the method that was detached, echoed so a caller batching several can tell the answers apart.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo billing portal methods rm <id>

.ts

.py

.go

.rs

.java

import { Configuration, BillingApi } from 'hanzoai';

const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteBillingPortalMethodsById({ id: 'id' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import BillingApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = BillingApi(client).delete_billing_portal_methods_by_id(id='id')

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.BillingAPI.DeleteBillingPortalMethodsById(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, billing_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = billing_api::delete_billing_portal_methods_by_id(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.BillingApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new BillingApi(client).deleteBillingPortalMethodsById();

curl -X DELETE https://api.hanzo.ai/v1/billing/portal/methods/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches billing through the billing tool, which names its 39 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_billing_accounts"
         }
       }
     }'

Billing API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousDelete methods — DELETE /v1/billing/methods/{id}NextList members