---
title: "Restore a User"
method: POST
path: "/api/users/restore/{id}"
tags: ["Users"]
---

# Restore a User

`POST /api/users/restore/{id}`

## Request

- Base URL: `https://app.timetastic.co.uk` (the document declares no server; this is the origin it was published from)
- URL: `https://app.timetastic.co.uk/api/users/restore/{id}`
- Auth: none declared

Use this to restore a user from Timetastic's Archive - they will be able to log in and use Timetastic as normal.
            
This endpoint is limited to 2 requests per second.
            
On success the body contains `wasEmailInUse`. When this is `true` the user was restored without their
original email address, because another active user has since taken it — set a new email address with
the edit endpoint before they can log in.

## Path parameters

- `id` integer, required

## Response `200`

The user was restored, e.g. `{ "wasEmailInUse": false }`.

## Other responses

- `400`: The user could not be restored. `errorStatus` says why.
- `401`: The request was not authenticated — the API token is missing or invalid.
- `403`: The authenticated user is not an administrator.
- `429`: The endpoint limit of 2 requests per second was exceeded.

---

[API](https://skmtc.dev/timetastic/apis/timetastic-api.md) · [All operations](https://skmtc.dev/timetastic/apis/timetastic-api/llms.txt) · [OpenAPI document](https://skmtc.dev/timetastic/apis/timetastic-api/revisions/709ccb0412c3?raw)