Sandbox
The sandbox is a live NolaPro install you can call without owning one. Sign up, mint a key, and start making requests — no licence, no install, no payment.
What you get#
Your first authenticated request provisions your own company inside the sandbox, along with the user your key acts as. Nobody else can see it, and you cannot see anyone else's — every record you create is tied to your company and filtered out of every other developer's results.
You do not create the company, choose its name, or manage it. It appears the first time you use a key, and it is yours until the nightly reset.
It is wiped every night#
The entire sandbox database is dropped and rebuilt nightly. Everything you created is gone: your company, your users, your invoices, your test data.
Your portal account, apps and keys survive — those live on developer.nolapro.com, not in the sandbox. The morning after a reset, your existing key provisions a fresh company on its first call and carries on working. You do not need to mint a new one.
Two things follow from that, and both matter more than they look:
- Do not build anything that assumes yesterday's ids still exist. A customer id you stored overnight will point at nothing, or worse, at a different record.
- A test that only passes on data you created last week will pass for the wrong reason, right up until the night it does not.
If you need data that outlives a day, seed it at the start of each run.
What is different from a real install#
The sandbox is the same code as every hosted NolaPro site, running the current release. The differences are deliberate:
| Sandbox | A real install | |
|---|---|---|
| Web interface | None — the API only | Full |
| Companies | One, yours, provisioned automatically | As many as you set up |
| Features | Nearly all enabled | Whatever you have licensed |
| Never sent | Sent | |
| Data | Wiped nightly | Yours |
| Cross-company requests | Not available | Available |
There is no login page. The sandbox serves the API and nothing else, so there is no screen to look at your data in. Read it back through the API, the same way your integration will.
Email is blocked at the transport. Anything that would send a message — an invoice, a statement, a password reset — will behave normally and deliver nothing. That is a feature: it means you can exercise those paths against real-looking addresses without mailing anyone.
Cross-company work cannot be tested here. Your key reaches exactly one company. If your integration needs to move between companies, you will need a real install to test against.
Rate limits#
Generous enough that ordinary development never notices, and low enough that a runaway loop stops before it becomes everyone's problem. If you hit one you get a 429 with a Retry-After header — wait that many seconds and continue.
Getting started#
- Create an account at developer.nolapro.com
- Confirm your email address
- Create an app — a named container for keys, one per integration
- Issue a key, choosing the narrowest set of scopes that does the job
- Make your first request; see Quickstart
The key is shown once, when it is created. Only its prefix is stored here, so if you lose it the only route forward is to revoke it and issue another.
When something stops working overnight#
Nine times in ten it is the reset, not a bug. Before investigating anything else, check whether you are using an id, a record or a piece of state created before the last wipe.