delete__organization_{orgId}_node_{nodeId}

DELETE /organization/{orgId}/node/{nodeId}

Delete Organization Node

Soft delete a node from the authenticated user's organization. This endpoint requires OWNER or ADMINISTRATOR role permissions and the node must belong to the specified organization. The node is not permanently removed but marked as deleted with a timestamp.

Important Notes:

• Only users with OWNER or ADMINISTRATOR roles can delete organization nodes

• This is a soft delete operation - the node is marked as deleted but not permanently removed

• Organization node quota will be decremented accordingly

• Deleted nodes can be reactivated using the appropriate activation endpoint

• The deletedAt field will be set to the current timestamp when the node is deleted

Path Parameters

Name	Type	Required	Description
» orgId	string	true	Unique identifier of the organization
» nodeId	string	true	Unique identifier of the node to delete

TypeScript Client Library

// Using the Flashback TypeScript client
import { FlashbackClient } from '@flashback/client';

const client = new FlashbackClient({
  accessToken: 'your-access-token'
});

// Delete an organization node
try {
  const result = await client.deletePrivateNode('org-id', 'node-id');
  console.log('Node deleted:', result);
} catch (error) {
  console.error('Failed to delete node:', error);
}

Code Samples

Shell

# You can also use wget
curl -X DELETE https://backend.flashback.tech/organization/550e8400-e29b-41d4-a716-446655440000/node/660e8400-e29b-41d4-a716-446655440001 \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer {access-token}'

HTTP

JavaScript

Ruby

Python

PHP

Java

Go

Example responses

200 Response

{
  "success": true,
  "message": "Node deleted successfully"
}

400 Response

{
  "success": false,
  "message": "Node is already deleted"
}

403 Response

{
  "success": false,
  "message": "Insufficient permissions: only OWNER and ADMINISTRATOR roles can manage nodes"
}

404 Response

{
  "success": false,
  "message": "Node not found"
}

500 Response

{
  "success": false,
  "message": "Internal server error"
}

Responses

Status	Meaning	Description	Schema
200	OK	Node deleted successfully	Inline
400	Bad Request	Node is already deleted	Inline
403	Forbidden	Insufficient permissions or access denied	Inline
404	Not Found	Node not found	Inline
500	Internal Server Error	Internal server error	Inline

Response Schema

Status Code 200

Name	Type	Required	Restrictions	Description
» success	boolean	false	none	Indicates if the request was successful
» message	string	false	none	Success message

Status Code 400

Name	Type	Required	Restrictions	Description
» success	boolean	false	none	Indicates if the request was successful
» message	string	false	none	Error message describing the issue

Status Code 403

Name	Type	Required	Restrictions	Description
» success	boolean	false	none	Indicates if the request was successful
» message	string	false	none	Error message describing the permission issue

Status Code 404

Name	Type	Required	Restrictions	Description
» success	boolean	false	none	Indicates if the request was successful
» message	string	false	none	Error message describing the issue

Status Code 500

Name	Type	Required	Restrictions	Description
» success	boolean	false	none	Indicates if the request was successful
» message	string	false	none	Error message describing the server issue

Security

• BearerAuth: Bearer token authentication required

• Permissions: Requires OWNER or ADMINISTRATOR role to manage organization nodes

• Organization Access: User must belong to the specified organization

• Node Ownership: Node must belong to the specified organization

Notes

• This is a soft delete operation - the node is marked as deleted with a timestamp but not permanently removed

• Only users with OWNER or ADMINISTRATOR roles can delete organization nodes

• Organization node quota will be decremented when a node is deleted

• Deleted nodes will not appear in node listing endpoints but their data is preserved

• A system event will be published when a node is successfully deleted

• Deleted nodes can be reactivated using the appropriate activation endpoint