Check billing, API and integrations

Billing and licences

• Check the organisation, product, plan, allowance and subscription state together.
• For payments, inspect the portal state and processed payment response; do not pay repeatedly.
• For invoices, compare the document type, period, state and available PDF/XML action.
• Read the confirmation and effective date of a licence change separately.

API diagnostics

1. Check the product and tenant host.
2. Use only the public schema as an integration contract.
3. Compare authentication type, capability and required permission.
4. Record the method, path, status code, request ID and time.
5. For 429, observe the stated wait time; for 5xx, inspect the business state before retrying.

401 means missing or expired authentication. 403 points to context or permission. 404 may indicate a record intentionally hidden in the active tenant. 409 commonly identifies a state or concurrency conflict.

Safe attachments

Use minimised example data. Remove Authorization, Cookie, X-API-KEY, webhook signatures, personal content and payment details. Repeat write requests only after idempotency or the previous state is clear.

Continue with API and integrations and Managing billing.