Support
Get help, in roughly this order.
Docs answer most of it. When they do not, the more of your run context you send, the faster this goes.
Documentation
Most questions about token formats, rate policy and run states are answered here first.
Read the docsCommunity
Adapter quirks, cohort patterns and workarounds, usually answered by people running the same setup.
Open communityAccount, billing and anything involving your data. We answer within one business day.
support@zenix.proSecurity
Report a vulnerability privately. Please do not open a public issue or post a proof of concept.
security@zenix.pro02/Before you write
What to include.
- Run idCopy it from any row in run history — the icon beside the short form copies the whole id. It carries the account, the proxy and the policy in one reference.
- What you expectedThe state you thought the run would reach, and what it reached instead.
- Network and account stateWhich adapter, and whether the session was showing valid at the time.
- Timestamp with timezoneRun history is UTC; telling us your local time costs a round trip.
Never send us a token · Support will never ask for a credential, and we cannot accept one. A run id and an account id are enough to find anything we need.