1. Create and confirm your account
Create a BusyIP account and confirm your email. The normal trial allowance is 1 GiB, once per account, without a credit card. When the monthly trial allocation has already been claimed, a smaller starter allowance applies.
Check the balance shown in your dashboard and read the trial details. Treat that visible allowance as the budget for your first set of tests.
2. Copy your own connection details
Your dashboard provides a username, secret, and proxy endpoints. Keep the secret in your usual password manager or development secret storage. Public documentation uses a fictional sample credential, which cannot authenticate your account.
Choose the endpoint your client supports: HTTP CONNECT or SOCKS5. Use the exact host and port supplied by the dashboard instead of guessing from a protocol’s conventional port number.
3. Verify a basic request first
Use the quickstart’s exit-IP request with your own credential. Begin without a country or type restriction so you can separate basic connection setup from the availability of a specific filtered exit.
Confirm that the request returns an address and check that your usage view reflects the test. If it does not connect, inspect the proxy configuration and the documented error information before trying a larger job.
4. Add the country or network type you need
BusyIP targeting markers are appended to the username. Add -type-residential for a home connection or -type-mobile for cellular. Add a country marker when your test needs an available country.
A matching participant must be online. If your filters cannot be served, the gateway returns a capacity error instead of quietly sending your traffic through a different location. The targeting table includes complete examples.
5. Choose how related requests stay together
If your work is a sequence of related requests, add a session identifier to pin an exit device. If requests are independent, rotating mode may be appropriate. In both cases, inspect the observed address if it affects your application.
Read the session guide before relying on a sticky session for an address-sensitive workflow. The device can remain selected while its carrier changes its address.
6. Set realistic client limits
A trial credential permits two concurrent connections. A single browser page can open several connections, so a “single test” in your code is not necessarily a single connection at the gateway.
Reduce parallelism for the first run and use clear timeouts. Add bounded retry handling for transient capacity problems, while keeping authorization and configuration errors visible.
7. Measure, then expand
Run a small sample of your actual permitted workflow and check the useful output, traffic consumption, and available coverage. If the result fits your needs, top up through your dashboard.
A purchase adds traffic to your current credential and raises paid concurrency to eight. The code you already verified can keep using the same username and secret. Your remaining traffic does not expire between jobs.
For the current endpoint details, targeting syntax, and error handling, use the BusyIP documentation. For pack prices and the complete metering disclosure, visit pricing.
Ask us about this guide →