Perception
Delete a saved extraction schema
- After: reading it, adding a version, or naming its schema_id on an extract answers 404 schema_not_found, and it leaves the list.
- Running extracts: an extract already accepted keeps the copy of the schema it took and finishes; its result still names the schema_id and schema_version it used.
- Repeats: deleting a schema that is already deleted answers 204 again.
- Nace's schemas (owner: "platform") can't be deleted; they answer 404.
- After: reading it, adding a version, or naming its
schema_idon an extract answers404 schema_not_found, and it leaves the list. - Running extracts: an extract already accepted keeps the copy of the schema it took and finishes; its result still names the
schema_idandschema_versionit used. - Repeats: deleting a schema that is already deleted answers
204again. - Nace's schemas (
owner: "platform") can't be deleted; they answer404.
Other errors (500, 502, 503) are on Errors.
Authorization
bearerAuth AuthorizationBearer <token>
Your API key, sent as Authorization: Bearer nace_sk_...
- Where: the dashboard's API Keys page. It is shown once, when you create it.
- Format:
nace_sk_followed by 43 URL-safe characters (A-Z,a-z,0-9,_and-). - Limit: an account can hold at most 3 active keys.
- Wrong or missing key: returns
401 authentication_error.
In: header
Path Parameters
idstringrequired
The schema's schema_id (sch_...). An id longer than 128 characters answers 404 with code not_found, not schema_not_found.
Length
length <= 128Response Body
application/json
application/json
application/json
curl -X DELETE "https://example.com/v1/extraction-schemas/string"Empty