# restoreEmployeeRevision

Put an AI employee back to a saved version (`revisionId` from listEmployeeRevisions): its instructions, settings, name and job title as that version held them (the avatar is kept, and a setting that version never had keeps its current value), saved as a new version. updateEmployeeConfig's checks apply, the screening one included. Pass `expectedUpdatedAt`. On an employee that is switched on it takes effect on its next run: needs their yes; a card’s counts.

- Call: `POST https://server.goliathdata.com/api/v1/call` with `{ "operationId": "restoreEmployeeRevision", "variables": {...} }`
- Scope: `WRITE`
- Type: mutation
- Idempotency: honors `Idempotency-Key` (24 h)
- Rate-limited: no

## Variables

- `employeeId`: `ID!` (required)
- `revisionId`: `ID!` (required)
- `acknowledgeScreeningWeakening`: `Boolean`
- `expectedUpdatedAt`: `DateTime`

## Response (data, an example)

```json
{
  "aiEmployeesMutation": {
    "restoreAiEmployeeRevision": {
      "id": "<ID>",
      "name": "…",
      "title": "…",
      "status": "ACTIVE",
      "updatedAt": "2026-01-01T00:00:00.000Z"
    }
  }
}
```

## Example

```bash
curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "operationId": "restoreEmployeeRevision",
    "variables": {
      "employeeId": "<employeeId>",
      "revisionId": "<revisionId>"
    }
  }'
```