delete__organization_users_{userId}

DELETE /organization/users/{userId}

Delete Organization User

Soft delete a user from the authenticated user's organization. This endpoint requires user management permissions (WORKSPACES role or higher) and both users must be in the same organization. The user is not permanently removed but marked as deleted with a timestamp.

Path Parameters

Name	Type	Required	Description
» userId	string	true	Unique identifier of the user 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 user
try {
  const result = await client.organization.users.delete('user-id');
  console.log('User deleted:', result);
} catch (error) {
  console.error('Failed to delete user:', error);
}

Code Samples

Shell

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

HTTP

DELETE https://backend.flashback.tech/organization/users/550e8400-e29b-41d4-a716-446655440000 HTTP/1.1
Host: localhost:3000
Accept: application/json
Authorization: Bearer {access-token}

JavaScript

const headers = {
  'Accept':'application/json',
  'Authorization':'Bearer {access-token}'
};

fetch('https://backend.flashback.tech/organization/users/550e8400-e29b-41d4-a716-446655440000',
{
  method: 'DELETE',
  headers: headers
})
.then(function(res) {
    return res.json();
}).then(function(body) {
    console.log(body);
});

Ruby

require 'rest-client'
require 'json'

headers = {
  'Accept' => 'application/json',
  'Authorization' => 'Bearer {access-token}'
}

result = RestClient.delete 'https://backend.flashback.tech/organization/users/550e8400-e29b-41d4-a716-446655440000',
  params: {
  }, headers: headers

p JSON.parse(result)

Python

import requests
headers = {
  'Accept': 'application/json',
  'Authorization': 'Bearer {access-token}'
}

r = requests.delete('https://backend.flashback.tech/organization/users/550e8400-e29b-41d4-a716-446655440000', headers = headers)

print(r.json())

PHP

<?php

require 'vendor/autoload.php';

$headers = array(
    'Accept' => 'application/json',
    'Authorization' => 'Bearer {access-token}',
);

$client = new \GuzzleHttp\Client();

try {
    $response = $client->request('DELETE','https://backend.flashback.tech/organization/users/550e8400-e29b-41d4-a716-446655440000', array(
        'headers' => $headers,
       )
    );
    print_r($response->getBody()->getContents());
 }
 catch (\GuzzleHttp\Exception\BadResponseException $e) {
    // handle exception or api errors.
    print_r($e->getMessage());
 }

Java

URL obj = new URL("https://backend.flashback.tech/organization/users/550e8400-e29b-41d4-a716-446655440000");
HttpURLConnection con = (HttpURLConnection) obj.openConnection();
con.setRequestMethod("DELETE");
con.setRequestProperty("Accept", "application/json");
con.setRequestProperty("Authorization", "Bearer {access-token}");
int responseCode = con.getResponseCode();
BufferedReader in = new BufferedReader(
    new InputStreamReader(con.getInputStream()));
String inputLine;
StringBuffer response = new StringBuffer();
while ((inputLine = in.readLine()) != null) {
    response.append(inputLine);
}
in.close();
System.out.println(response.toString());

Go

package main

import (
       "bytes"
       "net/http"
)

func main() {

    headers := map[string][]string{
        "Accept": []string{"application/json"},
        "Authorization": []string{"Bearer {access-token}"},
    }

    data := bytes.NewBuffer([]byte{})
    req, err := http.NewRequest("DELETE", "https://backend.flashback.tech/organization/users/550e8400-e29b-41d4-a716-446655440000", data)
    req.Header = headers

    client := &http.Client{}
    resp, err := client.Do(req)
    // ...
}

Example responses

200 Response

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

400 Response

{
  "success": false,
  "message": "Cannot delete yourself"
}

403 Response

{
  "success": false,
  "message": "Insufficient permissions to delete users"
}

404 Response

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

500 Response

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

Responses

Status	Meaning	Description	Schema
200	OK	User deleted successfully	Inline
400	Bad Request	Cannot delete yourself	Inline
403	Forbidden	Insufficient permissions or users not in same organization	Inline
404	Not Found	User 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 WORKSPACES role or higher to access user management functions

• Organization Access: Both users must be in the same organization

• Role Modification: Current user must have sufficient permissions to modify the target user's role

Notes

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

• Users cannot delete themselves through this endpoint

• Deleted users can be reactivated using the /organization/users/{userId}/activate endpoint

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

• Deleted users will not appear in user listing endpoints but their data is preserved