Company
Two inboxes and a voicemail box
Almost everything that reaches a person here reaches them by email, and there is now a number that takes messages as well. This page says which route to use, what to put in the message, and what we do not commit to about how fast you hear back.
What we do not offer
There is no live chat widget, no ticket portal, no switchboard and no office you can visit, and the number below is a voicemail box rather than a staffed line. A previous version of this page published a phone number alongside staffed business hours and a four-business-hour reply promise; the hours and the promise did not exist, and we still do not make either claim.
Where to write
Pick by subject rather than by urgency. Both addresses go to email, and neither is faster because you marked it important.
support@roamingproxy.com
Technical questions, failing requests, error codes, key rotation, account access, region requests, abuse reports and data-rights requests.
+1 (888) 527-9275
A voicemail line. Leave your account email address and what went wrong, and we come back to you. Nobody picks it up live, and it is not monitored to a schedule we are willing to publish — so anything time-sensitive is still better sent to support@roamingproxy.com, where it is written down.
billing@roamingproxy.com
Pricing, quotes, invoices, prepaid credits, credit notes and anything you dispute on a charge. The Terms ask you to raise disputes here before your bank.
The addresses the legal pages name
The Terms of Service also list legal@roamingproxy.com and abuse@roamingproxy.com; the Privacy Policy lists privacy@roamingproxy.com. If you are unsure, support@ is the one to use.
What to include so the reply is useful
For anything about a failing call, send the machine-readable error code from the response body — every data-plane refusal carries a stable one — plus the endpoint you called, the region you asked for, and the timestamp with its timezone. A refusal is exactly two fields, detail and code, so those four things are what there is to send.
If the fetch succeeded and the problem is what came back, the envelope carries more: device_id names the node that served it, region_used names the region that actually answered, public_ip is the address the target saw, and status is what the target itself replied. Quote those. A proxy fetch carries no request id — that field exists only on the social data API envelope — so the node, the region, the address and the timestamp are what we correlate our own records against.
Send the first characters of the API key if it helps identify the account. Never send the whole key, and never send your password. If you think a key has leaked, revoke it in the dashboard first and tell us afterwards.
Questions you can answer faster than we can
The API reference at api.roamingproxy.com/v2/docs is public and does not require an account. GET /v2/proxy/regions returns which regions are healthy right now, and GET /v2/proxy/status reports the fetch path's health. The dashboard's usage page shows what has been metered against your account per request.
How long we take
We publish three response commitments and no others. The Terms state we aim to respond to abuse reports within two business days. The Privacy Policy states we will answer a data-rights request within 30 days. And the 403 an unverified trial account gets from the proxy says that if you write to support@roamingproxy.com from the address on the account, we will verify it by hand, usually within one business day.
Everything else has no published target. Inventing one we have not measured would be the same mistake the old version of this page made, and a number nobody tracks is worse than no number at all.
Questions
- Is there a phone number?
- Yes: +1 (888) 527-9275. It is a voicemail box, not a switchboard — leave your account email address and what went wrong and we come back to you. We publish no answering hours and no callback time, because we have not measured one. The number the OLD site published was different, was never ours to answer, and is gone.
- Is there a contact form?
- No. A form would post to an endpoint that does not exist. Write to support@roamingproxy.com from any address you can read replies at.
- Who do I tell about a leaked API key?
- Revoke it yourself in the dashboard first — keys are individually revocable and scoped — then email support@roamingproxy.com. Under the Terms you are responsible for activity under a key until it is revoked, so the order matters.
Get a key
Create an account and mint an API key in the dashboard. The full endpoint reference — request shapes, parameters and error codes — is published at https://api.roamingproxy.com/v2/docs.