POST /v1/accounting/xero/connect

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin billing.invoice.manage; 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 POST https://api.zinndigital.com/v1/accounting/xero/connect \
  -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

Returns the Xero authorization URL to send the customer to. The URL carries a signed, short-lived `state` that names the organization and the actor — the callback has no other authority, because Xero redirects a browser to it with no credential of ours. `409 ACCOUNTING_CONNECTION_REFUSED` means **our** Xero application has no free organization slot, not that the caller did anything wrong. `422 FEATURE_NOT_INCLUDED` means the plan does not include accounting sync and it has not been bought as an add-on. Requires `billing.invoice.manage`.

Martani

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 409 · 422 · 429