Delete Transaction

cURL

curl --request DELETE \
  --url https://public.api.live.turrisfi.com/v1/policies/{policyId}/transactions/{transactionId}

const options = {method: 'DELETE'};

fetch('https://public.api.live.turrisfi.com/v1/policies/{policyId}/transactions/{transactionId}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

{
  "statusCode": 123,
  "requestId": "<string>",
  "errorType": "validation_error",
  "errorMessage": [
    "<string>"
  ],
  "timestamp": "<string>",
  "details": {}
}

{
  "statusCode": 123,
  "requestId": "<string>",
  "errorType": "validation_error",
  "errorMessage": [
    "<string>"
  ],
  "timestamp": "<string>",
  "details": {}
}

{
  "statusCode": 123,
  "requestId": "<string>",
  "errorType": "validation_error",
  "errorMessage": [
    "<string>"
  ],
  "timestamp": "<string>",
  "details": {}
}

DELETE

policies

{policyId}

transactions

{transactionId}

cURL

curl --request DELETE \
  --url https://public.api.live.turrisfi.com/v1/policies/{policyId}/transactions/{transactionId}

const options = {method: 'DELETE'};

fetch('https://public.api.live.turrisfi.com/v1/policies/{policyId}/transactions/{transactionId}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

{
  "statusCode": 123,
  "requestId": "<string>",
  "errorType": "validation_error",
  "errorMessage": [
    "<string>"
  ],
  "timestamp": "<string>",
  "details": {}
}

{
  "statusCode": 123,
  "requestId": "<string>",
  "errorType": "validation_error",
  "errorMessage": [
    "<string>"
  ],
  "timestamp": "<string>",
  "details": {}
}

{
  "statusCode": 123,
  "requestId": "<string>",
  "errorType": "validation_error",
  "errorMessage": [
    "<string>"
  ],
  "timestamp": "<string>",
  "details": {}
}

Permanently deletes a single transaction. This is a hard delete, not a soft delete. Both the parent policy and the transaction must belong to the authenticated upstream entity.

This action cannot be undone.

Path Parameters

Parameter	Type	Required	Description
`policyId`	string	Yes	Unique identifier of the parent policy (MongoDB ObjectId)
`transactionId`	string	Yes	Unique identifier of the transaction (MongoDB ObjectId)

Response

Returns 204 No Content on success with an empty body.

Error Scenarios

Bad Request (400)

Returned when policyId or transactionId is not a valid MongoDB ObjectId format.

{
  "statusCode": 400,
  "errorType": "validation_error",
  "errorMessage": ["transactionId must be a mongodb id"],
  "requestId": "dev-abc123",
  "timestamp": "2025-01-15T10:30:00.000Z"
}

Transaction Not Found (404)

Returned when the transaction does not exist under the policy, or belongs to a different upstream entity.

{
  "statusCode": 404,
  "errorType": "not_found",
  "errorMessage": ["Transaction not found"],
  "requestId": "dev-abc123",
  "timestamp": "2025-01-15T10:30:00.000Z"
}

Unauthorized (401)

Missing or invalid authentication token. See Authentication.

Path Parameters

policyId

string

required

Unique identifier of the parent policy

Example:

"6650a1b2c3d4e5f6a7b8c9d0"

transactionId

string

required

Unique identifier of the transaction

Example:

"6650a1b2c3d4e5f6a7b8c9d1"

Response

Transaction permanently deleted

Start Here

Shared Endpoints

Products

Agencies You Appoint

Contract Container Templates

Agents

Contacts

Market Contacts

Licenses

Appointments

Compliance Data Subscriptions

Compliance Status

File Documents

Policy Ingestion

Policy Transactions

Surplus Lines Filings

Webhooks

E&O/Cyber Compliance

Regulatory Actions

Tools

Path Parameters

Response

Error Scenarios

Bad Request (400)

Transaction Not Found (404)

Unauthorized (401)

Path Parameters

Response

​Path Parameters

​Response

​Error Scenarios

​Bad Request (400)

​Transaction Not Found (404)

​Unauthorized (401)

Path Parameters

Response

Path Parameters

Response

Error Scenarios

Bad Request (400)

Transaction Not Found (404)

Unauthorized (401)