Delete employee journal entry
Soft deletes an employee journal entry. The entry is marked as deleted but not permanently removed from the database.
What happens:
- The journal entry is marked with a
deletedAttimestamp - The entry will no longer appear in list queries or be accessible via the API
- The data is preserved in the database for audit purposes
- The entry cannot be restored through the API (restoration would require database access)
Access control:
- Users with
Employees.editpermission can delete any journal entry - Employees can delete their own entries (creator or subject)
- Returns 404 if the entry does not exist, has already been deleted, or the user does not have access
Note: This is a soft delete operation. The entry is not permanently removed and can potentially be recovered by database administrators if needed.
DELETE
/employees/journal/{id}Authorization
AuthorizationOAuth2 access token · headerrequiredScopes:
api:writeor
AuthorizationBearer token (JWT) · headerrequiredPath parameters
idstringrequiredResponses
200
successbooleanrequiredOperation success flag
401Unauthorized - Invalid or missing authentication token
403Forbidden - Insufficient API scopes or permissions
Request
curl -X DELETE "https://leadtime.app/api/public/employees/journal/string" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"const response = await fetch("https://leadtime.app/api/public/employees/journal/string", {
method: "DELETE",
headers: {
"Authorization": "Bearer YOUR_ACCESS_TOKEN"
}
});import requests
response = requests.delete(
"https://leadtime.app/api/public/employees/journal/string",
headers={
"Authorization": "Bearer YOUR_ACCESS_TOKEN"
},
)Response
{
"success": true
}Unauthorized - Invalid or missing authentication token
Forbidden - Insufficient API scopes or permissions