Skip to main content

Delete Package Config

Delete a matching package config by ID. The delete cascades to every run created from the config and is permanent, so export run history you need first.

Delete a matching package config by its UUID. The delete cascades: every package run created from this config is removed along with it. The config must belong to your organization, and this endpoint requires the write scope.

Because the cascade removes run history, deleting a config is destructive. If you need to keep the runs for audit, export them via the runs list endpoint before deleting. Deletion is permanent and cannot be undone.

The lookup is tenant-scoped. Attempting to delete a config that does not exist, or that belongs to another organization, returns 404 not_found. A successful delete returns the service confirmation payload.

Deleting a package config cascades to its runs. Export any run history you need to retain before calling this endpoint, because the delete is permanent.
DELETE/v1/matching/packages/configs/{id}

Path parameters

id*stringUUID of the package config to delete. Must belong to your organization.

curl

Response

Response fields

deletedbooleanTrue when the config and its runs were removed.

Response

{
  "deleted": true
}

Errors

Error responses

400validation_errorInvalid config ID format. Must be a UUID.
401unauthorizedMissing or invalid API key.
404not_foundNo package config with this ID exists for your organization.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.

Related

Get Package Config
List Package Configs