billing

GET /v1/accounting/xero/oauth/callback

Where Xero returns the customer after they authorize us.

Gbogbo àwọn billing 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/accounting/xero/oauth/callback

Ṣé 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ẹ̀

⛔ **Not called by a client** — Xero redirects the customer's browser here, so it is unauthenticated by necessity and all of its authority comes from the signed `state` minted by `startXeroConnect`. A missing, tampered or expired state is refused identically, and told apart only in our logs. Always answers with a 302 back to the dashboard rather than JSON, because the caller is a person in a browser. The outcome is carried in the query string.

Àwọn ìpìlẹ̀

OrúkọIruTí a nílòKini o jẹ
code (query)stringBẹẹkọXero's authorization code.
state (query)stringBẹẹkọThe signed state minted by `startXeroConnect`.
error (query)stringBẹẹkọPresent when the customer declined on Xero's consent screen.