Contact

For questions about the Partner API, the MCP server, the CLI, or anything in this documentation, email support@getcount.com.

Include your clientId, the endpoint and HTTP method, the timestamp of the request, and the requestId from the error body if you have one. Those four things are usually enough to find the request in COUNT's logs without a round trip. Never send your clientSecret or a customer's access token.

Before writing in, the errors and troubleshooting page covers the failures that come up most: signing mistakes, expired timestamps, token problems, and rate limits.

Partner credentials are issued after review rather than self-serve. Apply through the partner application form, and see the partner programme page for what the review covers and what you will be asked for.

For questions about using COUNT itself rather than building against it — a workspace, billing, or an accounting question — use the help centre at help.getcount.com or support.getcount.com.

If you believe you have found a vulnerability in the Partner API, the MCP server, or COUNT itself, report it to support@getcount.com with enough detail to reproduce it, and give COUNT a chance to fix it before disclosing it publicly. COUNT's security posture and compliance documentation are published at trust.getcount.com.

Live API and platform status is published at status.getcount.com. Check there before reporting a widespread failure — if an incident is open, the status page is updated ahead of individual support replies.

COUNT is operated by COUNT Financial Inc. General company contact details are at getcount.com/us/contact.