hosting

POST /v1/sites/{siteId}/ide-events

Record something the customer did in the site's web editor.

Dukkan hosting wuraren ƙarshe

Tabbatar da Asali

Wannan yankin ƙarshen jama'a ne. Ba ya ɗaukar wata takardar shaida ko ƙungiya — shi ne abin da shafin kasuwancinmu da injunan amsa na AI ke karantawa.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/ide-events \
  -H "Content-Type: application/json" \
  -d '{ "event": <string<file_saved, ai_applied, file_restored, terminal_opened>> }'

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

Appends one row to the site's activity log for an action taken in the editor — a file saved, an AI suggestion applied, an earlier version restored, a terminal opened. Editing the files of a live website is a privileged action and is logged as one. The acting person is taken from the **grant**, which the engine signed when the editor was opened, and never from the request: the caller runs inside the cage being audited, so anything it claimed about identity would be a claim by its own subject. The event name is mapped to a closed set of audit actions for the same reason. **This records what the editor did.** A customer with a terminal can change their own files without it, so it is an accountability trail for actions taken through our tool rather than a filesystem-level record. The filesystem-level answer is the site backup.

Sigogi

SunaNau'iAna buƙataAbin da yake
siteId (path)UuidEhSite ID (UUIDv7).

Jikin buƙata

SunaNau'iAna buƙataAbin da yake
eventstring<file_saved, ai_applied, file_restored, terminal_opened>EhA closed set. The caller runs inside the cage being audited, so it names an event and the engine chooses the audit action — a log whose rows can be authored by their own subject…
pathstringA'aThe file, relative to the site. Truncated to 512 characters.
bytes_beforeintegerA'aSize of the file before the write, so a truncation is visible in the log.
bytes_afterintegerA'a
versionstringA'aWhich kept version was restored, for a `file_restored` event.

Martani

SunaNau'iAna buƙataAbin da yake
recordedbooleanEh

Kuskuren da wannan matsaya za ta iya maido wa

404 · 422