---
title: "Decline Verification"
method: POST
path: "/signup/verify/decline"
tags: ["signup"]
---

# Decline Verification

`POST /signup/verify/decline`

## Request

- Base URL: `https://app.zeno-works.ch` (the document declares no server; this is the origin it was published from)
- URL: `https://app.zeno-works.ch/signup/verify/decline`
- Auth: none declared

*I did not ask for this.* **Tell the waiting agent, and create nothing.**

Two situations reach this button and neither can produce an account the person wants:
the address already has one, or they did not start this. In both, a waiting agent would
otherwise poll `pending` for the full TTL and then report `expired` — a long wait ending
in a wrong diagnosis.

**Not an enumeration oracle.** Causing this state requires the activation token, which
is 256 bits, stored only as a hash, and delivered *only in the mail to the address
itself* — it is never returned to whoever started the request. The party who can trigger
it is the mailbox owner, who already knows the answer, and the response is a constant.

Idempotent, and silent about failure for the same reason: an unknown, expired, claimed
or already-declined token gets the identical acknowledgement.

## Request body

- VerifyDeclineIn
  - `token` string, required

## Response `200`

Successful Response

- VerifyDeclineOut: One constant, always. Idempotent: an unknown, expired, claimed or already-declined token gets the identical acknowledgement, so the caller learns nothing either way.
  - `status` string

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/zeno-works/apis/zeno-api.md) · [All operations](https://skmtc.dev/zeno-works/apis/zeno-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zeno-works/apis/zeno-api/revisions/1eb93dde146c?raw)
