This endpoint builds and executes aDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/tutosrive/factus_challenge/llms.txt
Use this file to discover all available pages before exploring further.
DELETE FROM … WHERE statement against the specified PostgreSQL table. The target row or rows are identified entirely through URL path parameters — no request body is required. The deleted record is returned via RETURNING *, giving the caller a final snapshot of the data that was removed.
Endpoint
Path Parameters
Name of the PostgreSQL table to delete from. Examples:
customer, products.Column name used in the
WHERE clause to identify which row(s) to delete. Using a unique column such as id is strongly recommended to avoid unintended mass deletions.The value that
:property must equal for a row to be deleted. Interpolated into the SQL as a string literal: WHERE {property} = '{value}'.Request Body
None. All targeting information is supplied through the URL path.Responses
200 — OK
Returned when at least one row was deleted (rowCount > 0).
Always
200 on success."Datos eliminados"The first deleted row as returned by
RETURNING *. If multiple rows were deleted, only rows[0] is included in the response — the rest are silently discarded.404 — Not Found
Returned whenrowCount === 0, meaning no rows matched the WHERE condition.
500 — Internal Server Error
Returned on any exception thrown by thepg driver (e.g., a foreign-key constraint prevents deletion, the table does not exist, or a connection error occurs).
Raw error from the
pg driver. Check error.code (e.g., "23503" for a foreign-key violation) and error.detail for PostgreSQL-level diagnostics.