# Account deactivation

User may deactivate their account if the associated key was compromised, or must be forgotten. To do this, ACME client must send a POST request to the ACME Account URL:

```
POST https://stica.peeringhub.io/acme/acct/6A1AD155B73D45448E7B832888C3EF54
Content-Type: application/jose+json
Content-Length: 461
{
  "protected" : BASE64URL(
    {
      "alg": "ES256",
      "nonce": "7699E1AAD33D492ABB7D5A5326DC7D41",
      "url": "https://stica.peeringhub.io/acme/acct/6A1AD155B73D45448E7B832888C3EF54",
      "kid": "https://stica.peeringhub.io/acme/acct/6A1AD155B73D45448E7B832888C3EF54"
    }
  ),
  "payload" : BASE64URL(
    {
      "status" : "deactivated"
    }
  ),
  "signature" : "<base64url-encoded signature>"
}
```

ACME server shall return 200 OK with the ACME Account object. Account status must be changed to "deactivated".

```
HTTP/1.1 200 OK
Replay-Nonce: 6ECE0681255347D0BB29FCE79E895FF1
Content-Type: application/json; charset=utf-8
Content-Length: 112
{
  "status" : "deactivated",
  "orders" : "https://stica.peeringhub.io/acme/orders/6A1AD155B73D45448E7B832888C3EF54"
}
```

ACME server doesn't provide interface for re-enabling account after deactivation.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.peeringhub.io/guides/generating-certificate/acme-protocol-reference/account-deactivation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.