Edit your comment

Vorschau

patchhttps://api.expiryedge.com/v2/comments/{id}

the comment's author (403 otherwise)60/min

Anfrage

curl -X PATCH 'https://api.expiryedge.com/v2/comments/com_123' \
  -H "Authorization: Bearer $EXPIRYEDGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "string"
}'

Antwort

{
  "id": "cm_9Qa1",
  "expiryId": "exp_4Tq9sLm2",
  "organization_id": "org_northwind",
  "text": "Board confirmed the renewal fee.",
  "userId": "u_71bXq",
  "username": "Priya Shah",
  "userEmail": "priya.shah@northwinddental.example",
  "source": "api",
  "timestamp": "2026-09-27T14:20:00.000Z"
}

Sets edited: true.

Pfadparameter

idstringerforderlich

Body-Parameter

application/json

textstringerforderlich
Plain text.
max length: 5000

Rückgabe

200

The edited comment.

idstring
expiryIdstring
organization_idstring
Missing on older comments.
textstring
HTML-escaped, newlines as <br>.
userIdstring
usernamestring
userEmailstring
editedboolean
sourcestring
api for comments made through the API.
timestampstring
UTC timestamp, ISO 8601. Every v1 response uses this form, never a raw Firestore Timestamp ({_seconds, _nanoseconds}).
format: date-time

Fehler

`400`	Invalid parameters or body (`VALIDATION_FAILED`; `details` names the fields).
`401`	Missing, invalid or expired token (`UNAUTHORIZED`).
`403`	Your role can't do this, or your account has no organization (`FORBIDDEN`).
`404`	No such record in your organization (records in other organizations are also 404).
`405`	Wrong HTTP method for this path; the `Allow` header lists the valid ones.
`429`	Too many requests for this endpoint from your IP. Wait `Retry-After` seconds.