# `SANDBOX_VALUE_NOT_ALLOWED` (HTTP 403): the sandbox key does not answer for that value

The endpoint is one the sandbox answers, but only for the sample values the documentation prints, and the request asked about something else.

A sandbox that answered for any input would be a free lookup API. Each operation accepts exactly the values its documentation publishes: the six test addresses on spaw.test, the seven test numbers in the 555-01XX fiction block, and the sample IP and postal address the API reference prints.

The request body has to carry those fields and nothing else. An extra field is refused rather than ignored, which is what keeps the options that would cost something — a callback URL, a forced refresh, the live carrier check, the deliverability check, the reverse-DNS and abuse-contact lookups — out of the sandbox.

The message names the values the endpoint would have answered for.

**What to do.** Send one of the documented sample values, or use your own sk_live_ key to ask about a real address, number or IP. Check the request is JSON: curl -d without Content-Type: application/json sends a form field, which is not one of the accepted bodies.

```json
{
    "success": false,
    "error": {
        "code": "SANDBOX_VALUE_NOT_ALLOWED",
        "message": "The sandbox key answers this endpoint only for the documented test addresses (deliverable@spaw.test, unverified@spaw.test, catch-all@spaw.test, disposable@spaw.test, role@spaw.test, undeliverable@spaw.test). Send them as JSON with Content-Type: application/json, or use a key of your own for anything else.",
        "request_id": "req_01m1kgdm4xngzmbmff68g94w0c"
    }
}
```

Reference: https://spaw.co/docs/errors/SANDBOX_VALUE_NOT_ALLOWED