POST /v1/connector/backup/complete

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/connector/backup/complete \
  -H "Content-Type: application/json" \
  -d '{ "job_id": <string>, "status": <string<uploaded, failed>> }'

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

Settles the job the plugin claimed. Same bearer token, same silent treatment of an unknown one. ⛔ **The reported `size_bytes` is a cross-check, not the record.** We HEAD the stored object ourselves, because a truncated upload that reports success is indistinguishable from a good one until somebody tries to restore it — and because a site could otherwise report `uploaded` having written nothing, leaving a restore button over an object that does not exist. A `failed` report settles the row so it is not left running for ever. The detail is kept for staff and never shown to the customer: it is untranslated English and can carry a filesystem path from their server.

Jikin buƙata

Kuskuren da wannan matsaya za ta iya maido wa

422 · 429