Skip to main content

Getting started

Here at Veris Labs we specialize in making your next project work seamlessly across the entire web!

Quickstart​

1. Sign up​

Create an account on the dashboard and confirm your email.

2. Declare a use case​

On the Use cases page, declare the website or app you'll automate. Once it's approved, claim your trial on the Overview page, then add funds or buy a package.

3. Copy your API key​

On the Overview page, click Copy key on the Account key card. See Authentication for package keys.

4. Make your first call​

Check your balance with the Get Balance endpoint:

curl -H "X-Api-Key: YOUR_API_KEY" https://api.verislabs.io/balance
{"balance": 1.00}

Why request-based?​

  • Request-based solutions are orders of magnitude more performant than browser-based counterparts. The end-to-end time required to access protected content is reduced from 30+ seconds to ~5 seconds and bandwidth consumption is reduced by 90% on average, because you don't have to load all the resources and execute all the JavaScript on the page.
  • We are ready to help you whenever you need it, just contact us and we will do our best to assist you.
  • Blazing fast API responses: our sensor generation endpoints answer in <10ms on average, so the ~5 seconds above is almost entirely network round-trips to your target, not time spent in our API.

Prerequisites​

  • Basic knowledge of TLS, HTTP
  • Basic knowledge of any programming language
  • API key from the dashboard
  • HTTP Proxy for intercepting traffic; We strongly recommend powhttp
  • HTTP Client that:
    • Maintains header order
    • Accurately matches Chrome (or other) TLS profile
    • Implements Chrome's (or other) h2 (and/or h3)
    • We recommend bogdanfinn's tls-client and derivatives, but you can also use any other HTTP client that meets the requirements above.

Dos and Don'ts​

  • On web targets always use Chrome's latest User-Agent. Chrome follows a monthly release cycle, once a new update is pushed please allow general internet traffic to migrate to it. Update your User-Agent approximately 3-7 days after new Chrome release for optimal performance.
  • On other targets ensure your attributes are up to date. This includes app versions, iOS/Android versions, and other relevant attributes. Outdated attributes may result in WAF flagging your traffic.
  • Use an HTTP Proxy - It's your friend! The Network tab in DevTools is known for inaccurately showing header order or actual header names.
  • Don't use rotating proxies - instead use sticky/static ones. Rotating proxies rotate the IP on every new request and it MAY result in WAF flagging your traffic.
  • Maintain coherence:
    • Location: When visiting a US website, make sure to use the en-US language and a US proxy.
    • Language: Pass the exact Accept-Language header value your HTTP client sends (e.g. en-US,en;q=0.9) as the language field
    • Header order: Chrome sends headers in a specific order, make sure to copy it exactly. An HTTP Proxy will help you with that.
    • TLS profile: Chrome has specific TLS profile, make sure to match it.
  • Stick to the same HTTP client, proxy, and cookie jar across the full flow. Otherwise, you will be blocked by WAF. Your interaction must appear as a single, coherent HTTP session to the target server.
  • Do not hesitate to contact us! We are there to help!