note

POST /api/admin/support/tickets/:id/note {text} (support.reply): an internal note, never mailed. Audited support.note.

Caller and authorization

Staff cookie session; permission support.reply. Write requests need same-origin JSON and X-Admin-CSRF from this session.

This is the private staff console on https://admin.handwrites.io. A personal API key, organisation token, student login or isolated app-testing credential does not authenticate this route.

Request contract

Location	Name	Required	Meaning
path	`id`	Yes	Use the ID from an authorized staff response; source validators reject malformed IDs.
header	`X-Admin-CSRF`	Yes	Session-bound token from the staff page; not a developer credential.

The following is the accepted request shape, expressed as JSON Schema. It is not a runnable example. Runtime refinements and operation rules also apply.

{
  "type": "object",
  "properties": {
    "text": {
      "type": "string",
      "minLength": 1,
      "maxLength": 5000,
      "description": "Internal note, never mailed. Service trims and enforces the 5,000-character limit."
    }
  },
  "required": [
    "text"
  ]
}

Response and failures

Success: 201. POST /api/admin/support/tickets/:id/note {text} (support.reply): an internal note, never mailed. Audited support.note.

The wrapper returns {error:{code,message}} for CloudError failures, attaches Request-Id, and disables caching. Handle 401 by signing in; show role refusal for 403 forbidden, reauthenticate only for step_up_required, and collect a reason for 400 reason_required. A CSRF failure needs a current page/session token, not blind retries. Operation-specific 404/409/413/422/502/503 errors retain their status. Honor Retry-After on 429.

Usage notes

Keep customer messages and attachment URLs out of general logs. Replies can send real email; notes remain internal. Render inbound HTML only in the console’s sandboxed, network-restricted frame.

Implementation contract

Source snapshot: admin/src/app/api/admin/support/tickets/[id]/note/route.ts. This reference describes the current working tree, not proof of deployment. The response service types and validators remain authoritative. The exact exported handler below makes conditional behavior reviewable. For helpers such as customer-routes or cloudRoute, see the shared API specification notes and the named service module.

/** POST /api/admin/support/tickets/:id/note {text} (support.reply): an internal note, never mailed. Audited support.note. */
export const POST = adminRoute("support.reply", async (request, ctx, { params }: Context) => {
  const id = ticketIdParam((await params).id);
  const { text } = await readBody(request, z.object({ text: z.string().min(1).max(MAX_NOTE + 100) }));
  return adminJson(await addNote(ctx, id, text), { status: 201 });
});

Do not use production customer data to test this operation. Use an authorized staff test account and a disposable target in an appropriate environment; email, deletion, role and credential mutations have real effects.

README — POST /api/admin/support/tickets/{id}/note

POST /api/admin/support/tickets/{id}/note#

Caller and authorization#

Request contract#

Response and failures#