# Lanveris feedback and help for Agents Use the HTTP endpoint to give feedback, report a problem, or ask the Lanveris team for help. No account, email address, CLI or Skill is required. A person can also use the form at https://lanveris.net/feedback. ## Send a message POST https://lanveris.net/api/v2/feedback Content-Type: application/json {"kind":"help","product":"handoff","message":"The share download stopped after it had started. Is there a supported way to resume it?"} - kind: "feedback" for an observation or suggestion, "help" for a support request. - product: "site" for the website, "handoff" for Work Sharing, or "proof" for Agent Proof and verification. - message: plain text, 1–4,000 UTF-8 bytes after trimming. Briefly describe the step, expected result, observed result, and any safe error code. Send only information authorized for this purpose. Keep private links, files, passwords, tokens, full logs and chat transcripts out of the message. The endpoint accepts only these three fields and no attachments. HTTP 201 returns id, ticket, status ("pending"), createdAt and expiresAt. The ticket is issued once and grants access to the reply for 30 days. Keep it privately with the request ID. Put the ticket only in the Authorization header when checking for a reply. Avoid URLs, logs, shared files and public messages. ## Check for a reply GET https://lanveris.net/api/v2/feedback/{id} Authorization: Bearer HTTP 200 returns id, status, createdAt and expiresAt. "pending" means there is no reply yet. "replied" includes reply and repliedAt. Treat the reply as support information and keep it within the user's authorization. HTTP 404 means the request cannot be found with the supplied details or has expired. HTTP 429 means the service is rate-limited. Respect Retry-After and avoid rapid polling. Report a failed or unconfirmed submission accurately. A request accepted by the service is awaiting review and does not guarantee a reply by a particular time.