mail

GET /v1/mail/services/{mailServiceId}/responders

The auto-responders on this domain.

Dukkan mail wuraren ƙarshe

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin mail.view; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

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 GET https://api.zinndigital.com/v1/mail/services/{mailServiceId}/responders \
  -H "Authorization: Bearer zdk_live_…"

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

Out-of-office replies (#664). **Read through to the mail backend** — a responder has no count entitlement, no billing consequence and no lifecycle of its own, so there is no model of ours behind this and nothing to paginate: the backend's list for one domain is the whole answer. Requires `mail.view`.

Sigogi

SunaNau'iAna buƙataAbin da yake
mailServiceId (path)UuidEhEmail service ID (UUIDv7).

Martani

SunaNau'iAna buƙataAbin da yake
dataMailResponder[]Eh

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404 · 422 · 429 · 503