Skip to content

Remove member

Removing a member via API

DELETE /organizations/{org_id}/users/{user_id}

This endpoint deactivates a member from your Tallyfy organization. The member loses access to this org, but their global Tallyfy account stays intact. You can optionally reassign their tasks to another member during removal.

Admin permissions are required. Bot users can’t be removed through this endpoint.

Separate permanent deletion flow

Tallyfy also offers a two-step permanent deletion flow using different endpoints:

  1. Disable: DELETE /organizations/{org_id}/users/{user_id}/disable
  2. Permanently delete: DELETE /organizations/{org_id}/users/{user_id}/delete

The permanent delete endpoint requires the member to be disabled first — you’ll get an error if you skip that step. The main DELETE /organizations/{org_id}/users/{user_id} endpoint documented here doesn’t require disabling first.

Request

Replace {org_id} with your Organization ID and {user_id} with the member’s numeric ID.

Headers

  • Authorization: Bearer {your_access_token}
  • Accept: application/json
  • X-Tallyfy-Client: APIClient

Query parameters (optional)

  • with_reassignment (boolean) - Set to true to reassign the member’s tasks before removal.
  • to (integer) - Required when with_reassignment=true. The user ID receiving reassigned tasks.

Example: ?with_reassignment=true&to=1002

Body

No request body needed.

Code samples

const accessToken = 'YOUR_PERSONAL_ACCESS_TOKEN';
const orgId = 'YOUR_ORGANIZATION_ID';
const userId = 12345;
const reassignToUserId = null; // Set to a user ID to reassign tasks
const params = new URLSearchParams();
if (reassignToUserId != null) {
params.append('with_reassignment', 'true');
params.append('to', reassignToUserId.toString());
}
const queryStr = params.toString();
const apiUrl = `https://go.tallyfy.com/api/organizations/${orgId}/users/${userId}${queryStr ? '?' + queryStr : ''}`;
fetch(apiUrl, {
method: 'DELETE',
headers: {
'Authorization': `Bearer ${accessToken}`,
'Accept': 'application/json',
'X-Tallyfy-Client': 'APIClient'
}
})
.then(response => {
if (!response.ok) {
return response.json().then(err => { throw new Error(JSON.stringify(err)); });
}
return response.json();
})
.then(data => {
console.log('Member removed:', JSON.stringify(data, null, 2));
})
.catch(error => {
console.error(`Error removing member ${userId}:`, error.message);
});

Response

Returns 200 OK with the removed member’s data wrapped in a data object.

Success response example

{
"data": {
"id": 12345,
"email": "john.doe@example.com",
"first_name": "John",
"last_name": "Doe",
"role": "standard",
"status": "disabled"
}
}

Error responses

StatusError messageWhat to do
400You can't remove a bot user from this organization!Bot users can’t be removed through this endpoint.
400Cannot modify the default administrator. Please assign another member as default administrator first.Assign the default admin role to someone else before removing this member.
404User not foundCheck that the user ID exists in this organization.

Org Settings > Member deletion

Deleting a member in Tallyfy requires first disabling them and then permanently removing them while handling common blockers like default admin restrictions and bot user limitations along with proper task reassignment and data retention for compliance.

Org Settings > Remove a member

Tallyfy requires admins to deactivate a member before deleting them and prompts reassignment of all pending tasks and template steps to another active member during removal while also protecting against accidental deletion of the last admin or default administrator account.

Members > How to remove a member

Administrators in Tallyfy can instantly remove a member by deactivating their account under Settings > Organization > Members and then choosing to either reassign that person’s open tasks to other team members or leave them unassigned for later handling.

Members > Get member

Tallyfy’s API lets admin users fetch a specific organization member’s profile by their numeric user ID through a GET request and optionally include related data like stats and groups and preferences in the response.