Create Sandbox Project From Feature
Create a sandbox project from a confirmed resolved feature (address entry).
The create-flow inversion: unlike POST /sandbox (county picked first), the county scope is derived from the matched feature before the project's RLS role is provisioned. Two-phase — this handler derives scope, inserts the PENDING project + role synchronously, and enqueues the async layer seed; status flips to ready and the layer arrives via SSE.
No available_geographies 403: the matched feature is in-coverage by construction (the resolver only searched this workspace's loaded sandbox). Unknown feature_id → 404; a county somehow not loaded → 404 before any project row is inserted; a matched feature whose _county_fips is NULL/malformed (a sandbox data-integrity fault, not a caller error) → 422.
Headers
Request body
Response
Successful Response
Changes
Changed in 4 of the 30 revisions of this API.33
- ▲
the request property
became requiredrequest-property-became-required
- ▲
request property
list-of-types was narrowed by removing typesnullfrom media typeapplication/jsonrequest-property-list-of-types-narrowed
- ▲
added the pattern
^\d{5}$to the request propertyrequest-property-pattern-added
- ▲
- ○
added the new optional request property
new-optional-request-property
- ○
- ○
added the new optional
headerrequest parameterIdempotency-Keynew-optional-request-parameter
- ○
- ○
added the new optional request property
new-optional-request-property
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○