notifications

GET /v1/notification-connections/confirm

What a confirmation link is asking.

Gbogbo àwọn notifications endpoints

Ìfàṣẹ́pọ̀

Ojú-wọ̀n yìí jẹ́ ti gbogbo ènìyàn. Kò gba àmì ìdánimọ̀ kankan tàbí àgbájọ kankan — ohun tí ojú-wọ̀n ìpolówó wa àti àwọn ẹ̀rọ ìdáhùn AI ǹkà kọ́ ni.

Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.

Gbiyanju rẹ

Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.

curl -X GET https://api.zinndigital.com/v1/notification-connections/confirm?token=<token>

Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API

Àwọn kúlẹ̀kúlẹ̀

Public and unauthenticated: the person clicking is very often an accountant or a colleague with no account here, and a confirmation behind a login wall cannot be completed by the one person it is addressed to. GET only DESCRIBES. Mail clients and scanners fetch links before a human sees them, so a confirming GET would be auto-clicked by the recipient's own mail infrastructure and double opt-in would silently become single opt-in. An unknown, expired or already-used token all answer `valid: false` identically - the endpoint must not become an oracle for which addresses an organisation has pending.

Àwọn ìpìlẹ̀

OrúkọIruTí a nílòKini o jẹ
token (query)stringBẹẹni

Idahun

OrúkọIruTí a nílòKini o jẹ
validbooleanBẹẹkọ
emailstringBẹẹkọ
organisationstringBẹẹkọ