Company
No demo call. A playground and your own URL
A demo is somebody else's happy path on somebody else's target. The question you actually have is whether your target answers a request from our addresses, and only your URL answers that.
What we do not offer
There is no scheduled demo, no screen share, no sales engineer, no proof-of-concept programme and no sandbox serving fake data. The old version of this page asked for your preferred demo date and promised contact within 24 hours to schedule it. No such calendar exists.
The short version, including the part that stops you
Create an account at cloud.roamingproxy.com. Mint an API key in the dashboard with the proxy scope. Then read the next paragraph before you open the playground, because there is a gate between a new account and its first fetch and we would rather you heard about it here than from a 403.
A trial account cannot send egress until its email address is verified. Until it is, the proxy refuses with 403 and the code email_verification_required. We are not going to pretend the verification mail is reliable right now, because it is not: mail delivery is the weak link, and the refusal itself names the way around it. Email support@roamingproxy.com from the address the account is registered under and we will verify it by hand, usually within one business day. An account with an active paid subscription skips the check entirely.
Once egress is open, the call is POST /v2/proxy/fetch with your key in an x-api-key header, the region as a query parameter, and a JSON body of {"url": "https://your-target"}. You get the target's status, content type and body back in a JSON envelope, along with the address the target saw and which node and region served the fetch. The target's own response headers are not part of the envelope. That is the entire product surface for the proxy.
What you can verify yourself, without asking us
Everything a demo would have shown you is readable from the API or the dashboard.
Whether your target responds
Paste the URL into the playground. A datacenter address either gets a page back or it does not.
Which regions are live
GET /v2/proxy/regions is health-gated, so a region missing from the list is one we will not serve right now.
What a request costs
The usage page shows per-request metering, and the same records are queryable over the API.
How failures behave
Every data-plane refusal carries a stable machine-readable code, pinned against the published API reference by a test.
That retries are safe
Send an Idempotency-Key, retry after a timeout, and the replay comes back marked Idempotency-Replayed without being executed or billed twice.
If you would rather ask a person first
Email support@roamingproxy.com with the target you care about and the region you want it fetched from. We will tell you what we think will happen. We will also tell you when the answer is no — search engines, sites that block cloud ranges, and anything that needs JavaScript executed are all outside what this service does.
Questions
- Can I book a call anyway?
- There is no booking system to book one with. Email works, and for a technical question it is usually faster than a meeting would be.
- Is there a sandbox with sample data?
- No. The playground calls the live API against the real target you give it, which is the only test worth running.
- What if my target blocks us?
- Then you have learned it from one fetch rather than after integrating. Our addresses are AWS ranges and recognisable as such; no amount of rotation inside our own fleet changes that.
- Why did my first fetch come back 403?
- Almost certainly the email verification gate — check the code field for email_verification_required. The refusal's own body spells out the way round it: write to support@roamingproxy.com from the account's own address and we will verify it by hand, usually within one business day. A paid subscription is not subject to the check.
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.