API · v1 · stabil
CODEMETA OSDeveloper Center
Konsole öffnen
Entity · expiry_trackers

Expiry Tracker Schema

Schema-ID
expiry_tracker
Collection
expiry_trackers
Permissions
  • Lesenexpiry_tracker_view
  • Anlegenexpiry_tracker_create
  • Ändernexpiry_tracker_edit
  • Löschenexpiry_tracker_delete
Beziehungen

Felder

Expiry Tracker Schema

expiry_trackers4 Permissions

Schema for validating expiry tracker entities

namestringerforderlich

Human-readable name, e.g. "Azure AD Secret – Webseiten-SMTP"

1–200 Zeichen
categorystringerforderlich

Type of the tracked item

Werte
SSL_CERTIFICATEAZURE_AD_SECRETAPPLE_PUSH_CERTIFICATESSO_CERTIFICATELICENSEDOMAINWARRANTYAPI_KEYOTHER
expiresAtdatetimeerforderlich

The critical expiry date

statusstringoptional

Lifecycle: ACTIVE (tracked), RENEWED (manually closed as renewed elsewhere), EXPIRED (auto-flipped after the date passed), DISMISSED (manually ignored)

Werte
ACTIVERENEWEDEXPIREDDISMISSED
Default: "ACTIVE"
partyIduuidoptional

Owning customer party; null = internal MSP-owned entry

nullable
assignedToIduuidoptional

Responsible user — recipient of the reminder actions

nullable
linkedAssetIduuidoptional→ asset

Optional related asset (domain/server/…)

nullable
secretIduuidoptional

Optional link to a vault secret. NEVER store the secret value here.

nullable
notesstringoptional

Free-text notes

max 2000 Zeichennullable
reminderDaysBeforeinteger[]optional

Escalation lead stages (days before expiry) at which actions fire

min 1 Itemsunique itemsDefault: []
actionsstring[]erforderlich

Actions to perform before expiry. NOTIFY = in-app + push. At least one is mandatory.

min 1 Itemsunique items
firedLeadsinteger[]optional

Lead stages (from reminderDaysBefore) that have already fired

Default: []read-only
lastNotifiedAtdatetimeoptional

Timestamp of the last fired reminder

read-onlynullable
createdCalendarEventIduuidoptional

Id of the auto-created calendar event (created once)

read-onlynullable
createdTicketIduuidoptional

Id of the auto-created ticket (created once)

read-onlynullable

Standard-Endpoints

Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:

  • GET /api/v1/expiry_trackers — Liste, paginiert + filterbar
  • GET /api/v1/expiry_trackers/<id> — Einzelne Entity
  • POST /api/v1/expiry_trackers — Anlegen
  • PATCH /api/v1/expiry_trackers/<id> — Teil-Update
  • DELETE /api/v1/expiry_trackers/<id> — Soft-Delete
  • GET /api/v1/expiry_trackers/<id>/timeline — Audit + Aktivitäten

Suche