PerceptionDocs

Delete a saved extraction schema

Deletes the schema with every version. Free, and works at any balance.

DELETE
/v1/extraction-schemas/{id}
  • 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.

Other errors (500, 502, 503) are on Errors.

Authorization

bearerAuth
AuthorizationBearer <token>

Your API key from the dashboard's API Keys page: nace_sk_ followed by 43 URL-safe characters (A-Z, a-z, 0-9, _ and -), shown once when you create it. Send it as Authorization: Bearer nace_sk_... Any other value returns 401 authentication_error. An account can hold at most 3 active keys.

In: header

Path Parameters

id*string

The schema's schema_id (sch_...). An id longer than 128 characters answers 404 with code not_found, not schema_not_found.

Lengthlength <= 128

Response Body

application/json

application/json

application/json

curl -X DELETE "https://example.com/v1/extraction-schemas/string"
Empty

Get a saved extraction schema GET

The schema's latest version.

List a schema's versions GET

Every version of one of the account's schemas.