Get the account's standing
Answers where the billing account stands on unpaid invoices: what is overdue, each invoice being followed up with its dates, the services that are suspended and what brings them back. A company with no billing account yet answers good with empty lists.
Query parameters
The billing account to read, by its id (see GET /corestack/billing/account). Left out, the request acts on your company's default billing account. An account that does not exist and one that is not your company's answer the same 404. At least 1.
The same as account, under the name the MCP tools use. Send one of the two: when they name different accounts the request is refused 422 invalid on account_id. At least 1.
Returns
200 The account's standing.
Fields of the 200 answer
The unpaid invoices being followed up, the one due first at the top.
Fields of each item
When the data is deleted. The same moment as retrieval_until. Format: date-time.
Whether the invoice has an open dispute.
Format: date-time.
When the final notice was sent. Format: date-time.
At least 1.
The invoice number.
What is left to pay on the invoice, in currency.
Whole days since the invoice was due.
Until when the data of ended services is kept. Format: date-time.
How far the follow-up has gone. final_notice: a final notice has been sent. suspended: the services are suspended. terminated: the services have ended and their data is kept until retrieval_until. settled_in_retrieval: the invoice was settled after the services ended. deleting: the data is being deleted.
final_noticesuspendedterminatedsettled_in_retrievaldeletingWhen the services are suspended if the invoice is still unpaid. Format: date-time.
Format: date-time.
When the services end if the invoice is still unpaid. Format: date-time.
Format: date-time.
When Corefinity has paused the follow-up for your company, until when. Format: date-time.
What brings suspended services back. how is none when nothing is suspended or the data is being deleted, pay_invoices while paying the invoices brings them back by itself, and staff_reinstatement once the services have ended and Corefinity has to reinstate them. The other fields depend on how.
Fields
Whether the services come back without anyone at Corefinity acting.
With staff_reinstatement, how to ask for it.
nonepay_invoicesstaff_reinstatementWith pay_invoices, the invoices to pay.
With pay_invoices, the page of each invoice in the Control Panel, as a path.
With pay_invoices, how soon the services are back once the payment has cleared.
With staff_reinstatement, until when the data is kept. Format: date-time.
With staff_reinstatement, whether the invoice has been paid.
The most advanced fact of the account. good: nothing is overdue. overdue: an invoice is past its due date. final_notice: a final notice has been sent. suspended: services are suspended. retrieval: services have ended and their data is still kept.
goodoverduefinal_noticesuspendedretrievalFields of each item
At least 1.
The site's domain or the CoreCluster's name. Empty when it is no longer your company's.
suspendedretrievalFormat: date-time.
siteclusterIf it is refused
| Status | Reason | What to do |
|---|---|---|
401 | none | Send a valid token as Authorization: Bearer <token>. |
403 | billing_forbidden | Billing is for the organisation's owner and billing contacts. Ask one of them to do this. |
403 | company_unavailable | Your company is unavailable. |
403 | scope_required | Use a token with the scope named in scope. |
403 | two_factor_required | Turn on two-factor on your account, then send again. |
404 | feature_off | This feature is not on for your organisation yet. |
422 | invalid | Fix the field named in field; errors says why. |
429 | rate_limited | Wait for the seconds in Retry-After. |
Reasons are listed by name in Errors and refusals.
The same task elsewhere
curl https://manage.corefinity.com/api/corestack/billing/standing \
-H "Authorization: Bearer $COREFINITY_TOKEN" \
-H "Accept: application/json"use Illuminate\Support\Facades\Http;
$response = Http::withToken(env('COREFINITY_TOKEN'))
->acceptJson()
->get('https://manage.corefinity.com/api/corestack/billing/standing');
$data = $response->json();const res = await fetch('https://manage.corefinity.com/api/corestack/billing/standing', {
method: 'GET',
headers: {
Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
Accept: 'application/json',
},
});
// An answer with no body (204) has nothing to parse.
const text = await res.text();
const data = text && JSON.parse(text);import os
import requests
res = requests.get(
"https://manage.corefinity.com/api/corestack/billing/standing",
headers={
"Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
"Accept": "application/json",
},
)
data = res.json() if res.content else None{
"cases": [
{
"currency": "GBP",
"delete_on": null,
"disputed": false,
"due_at": "2026-11-01T00:00:00Z",
"final_notice_at": "2026-11-07T06:00:00Z",
"invoice_id": 8140,
"number": "CF-100057",
"outstanding": 240,
"overdue_days": 8,
"retrieval_until": null,
"stage": "final_notice",
"suspend_on": "2026-11-16T10:00:00Z",
"suspended_at": null,
"terminate_on": null,
"terminated_at": null
}
],
"paused_until": null,
"restore": {
"how": "none"
},
"state": "final_notice",
"suspended_services": []
}{
"message": "Unauthenticated."
}{
"code": "billing_forbidden",
"message": "Billing is available to your company's owner and billing contacts.",
"reason": "billing_forbidden"
}{
"code": "feature_off",
"message": "Not found.",
"reason": "feature_off"
}{
"code": "invalid",
"errors": {
"account_id": [
"Send account or account_id, not both: they name different billing accounts."
]
},
"field": "account_id",
"message": "Send account or account_id, not both: they name different billing accounts.",
"reason": "invalid"
}{
"code": "rate_limited",
"message": "Too many requests. Try again in 60 seconds.",
"reason": "rate_limited",
"retry_after_seconds": 60
}