Update an expiry workflow attachment

posthttps://api.expiryedge.com/v1/updateExpiryWorkflowAttachment

editor or admin60/minJede Methode

Anfrage

curl -X POST 'https://api.expiryedge.com/v1/updateExpiryWorkflowAttachment?id=att_1Mz7' \
  -H "Authorization: Bearer $EXPIRYEDGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "trigger_type": "before_expiry",
  "trigger_days": 45,
  "trigger_time": "08:30"
}'

Antwort

{
  "message": "Attachment updated",
  "attachment_id": "att_1Mz7"
}

Id in ?id= (or attachment_id in query or body). Changing trigger_type recomputes trigger_date and resets a not-yet-fired trigger to pending (paused for manual). Notification settings must be sent nested in notification_config here (flat fields are ignored on update). The web app sends PUT; any HTTP method is accepted.

Query-Parameter

idstring
Attachment id.

Body-Parameter

application/json

attachment_idstring
Alternative to ?id=.
trigger_typestring
Erlaubtbefore_expiryon_expiryafter_expiryon_doneon_renewalmanual
trigger_daysinteger
min: 0 · max: 365
trigger_timestring
pattern: ^\d{2}:\d{2}$
carry_to_renewalboolean
notification_configobject

Rückgabe

200

Updated.

messagestringerforderlich
attachment_idstringerforderlich

Fehler

`400`	The request is missing required fields or contains invalid values.
`401`	Missing, expired or invalid bearer token.
`403`	Authenticated, but your role or organization does not allow this action.
`404`	The record does not exist or is not in your organization.
`429`	Too many requests for this endpoint from your IP. Wait `Retry-After` seconds.
`500`	Unexpected server error. Retry later; quote `requestId` to support.