Sandbox

A test environment for the ShipReal API. It runs the same code as production over frozen fixture data, so you can write an integration test, try a client generator, or let an agent rehearse a call sequence without depending on the real curriculum staying still.

No key, no account, no signup, exactly like production. The difference is the data behind it, not the way you reach it.

Base URL

Insert /sandbox after the API version. Everything after that is identical to the live path.

# Live
curl "https://shipreal.dev/api/v1/modules?q=caching"

# Sandbox
curl "https://shipreal.dev/api/v1/sandbox/modules?q=caching"

What is in it

Why the numbers look wrong

They are meant to. Fixture prices are 1 unit and fixture module URLs point at example.invalid, a domain reserved by RFC 6761 that can never resolve. If a sandbox value reaches a user or a purchase flow, it should be obvious at a glance that it came from the wrong environment, and a link built from it should fail loudly rather than quietly go somewhere real.

Assert on shape, pagination, headers and error format. Do not assert on prices or titles: the fixtures are stable, but they are not the course.

What behaves identically

Pagination, cursors, RateLimit-* headers, and RFC 9457 problem details for errors. A 404 in the sandbox is the same document shape as a 404 in production, which is the point: a test that passes here exercises the paths your code actually takes.

# Same problem+json shape as production
curl -i "https://shipreal.dev/api/v1/sandbox/modules/does-not-exist"

There is still nothing to write

The sandbox is not a payment test mode, because the API has no write path in either environment. Enrollment runs through a hosted checkout, so there is no transaction for an agent to rehearse and no test card to spend. If you are looking for how buying works, read pricing and the developer notes.