Skip to content
RocketVerifierDOCS

Get started

Verify your first email in 5 minutes

In short

Create an API key in the dashboard, send one POST request to https://api.rocketverifier.com/v1/verify with the address, and branch on the status field. Use sandbox addresses to test for free.

On this page

You need a RocketVerifier account and about five minutes. By the end you will have verified a real address and know what to do with each result.

  1. Create an API key

    Open API keys in the dashboard and create a key. Live keys start with rv_live_ and verify any address. Sandbox keys start with rv_test_ and only accept sandbox addresses, which makes them safe for CI.

    Store the key in an environment variable and pass it to the client. Every example in these docs reads ROCKETVERIFIER_API_KEY, and the CLI picks it up automatically.

    export ROCKETVERIFIER_API_KEY="rv_live_your_key_here"
  2. Install an SDK (optional)

    npm install @rocketverifier/sdk
  3. Verify an address

    Start with a sandbox address. It returns a fixed result and costs nothing, so you can check your integration before you spend a credit.

    import RocketVerifier from "@rocketverifier/sdk";
    
    const rv = new RocketVerifier(process.env.ROCKETVERIFIER_API_KEY);
    const result = await rv.verify("deliverable@sandbox.rocketverifier.com");
    
    console.log(result.status);    // "deliverable"
    console.log(result.subStatus); // "none"
    console.log(result.score);     // 95

    Then swap in a real address. Real addresses need a live key and use 1 credit per result, except unknown results, which are free.

  4. Act on the result

    Branch on status. It always holds one of four values, and the decision for each is the same in every product.

    deliverable1 credit

    Send

    The mail server explicitly accepted the mailbox.

    undeliverable1 credit

    Remove

    The address will bounce: the mailbox, domain or syntax is invalid, or the address is disposable.

    risky1 credit

    Send with care

    The address accepts mail but carries a risk: catch-all domain, role address, full mailbox, trap or abuse signals.

    unknownFree

    Retry later

    The mail server gave no conclusive answer. Retry after retry_after seconds.

    Node.js
    switch (result.status) {
      case "deliverable":
        return accept(email);
      case "risky":
        // catch-all, role address, full mailbox: accept, but flag for review
        return acceptWithFlag(email, result.subStatus);
      case "undeliverable":
        return reject(email, result.didYouMean ? `Did you mean ${result.didYouMean}?` : undefined);
      case "unknown":
        // free: check again later
        return queueRetry(email);
    }

Try it now#

No key needed. These calls hit the live API with sandbox addresses.

Sandbox addresses return fixed results from the live API. No key, no credits.

Next steps#

Frequently asked questions

Do I need a credit card to start?

No. Sign up, create a key and test with sandbox addresses for free. Buy credits when you are ready to verify real addresses.

Which status means I can send?

deliverable means the mail server confirmed the mailbox. Treat risky with care, remove undeliverable, and retry unknown later at no cost.

Should I use the SDK or plain HTTP?

Either. The SDKs add retries on rate limits, typed results and helpers for bulk jobs and webhooks. Plain HTTP works from any language with one POST request.

Updated 11 November 2026Suggest an edit