compute

POST /v1/compute/eligibility

Submit an organisation for verification.

Semua titik akhir compute

Autentikasi

Kirim kunci API sebagai token bearer. Kunci tersebut harus memiliki izin billing.payment.manage; kunci tanpa izin tersebut akan ditolak dengan status 403, bukan 404.

Tempat ID organisasi Anda dimasukkan

Titik akhir ini menerima org_id sebagai parameter kueri. Kosongkan parameter tersebut dan panggilan ini akan mencakup seluruh subpohon penyewa Anda; kirimkan untuk mempersempit panggilan ke satu organisasi.

ID organisasi Anda berada di layar kunci API di dasbor Anda, di sebelah kunci itu sendiri. Itu adalah ID yang sama dalam setiap panggilan yang Anda buat.

Coba

Ganti apa pun di dalam tanda kurung sudut dengan nilai Anda sendiri, dan placeholder kunci dengan kunci dari dasbor Anda.

curl -X POST https://api.zinndigital.com/v1/compute/eligibility \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "legal_name": <string>, "country": <string>, "abuse_contact_email": <string> }'

Sudah masuk? Konsol API di dasbor Anda akan mengisi ID organisasi asli dan kunci Anda sendiri, serta menjalankan permintaan terhadap API langsung sehingga Anda dapat melihat respons aktualnya. Buka titik akhir ini di konsol API

Detail

Moves the organisation to `pending` for a human to review. **202**, because the answer is a decision somebody makes rather than something this call performs. ⛔ An organisation that is already verified, or already pending, is refused `422` rather than silently re-queued: resubmitting would otherwise let a customer suspend their own verification, and let a rejected applicant re-enter the queue for ever. Requires `billing.payment.manage` — ⛔ **not** `billing.entitlement.manage`, a staff key no customer role holds, which is what this said until D10689.

Parameter

NamaJenisWajibTentang apa ini
org_id (query)UuidTidak

Isi permintaan

NamaJenisWajibTentang apa ini
legal_namestringYa
countrystringYa
abuse_contact_emailstringYa
company_numberstringTidak
intended_usestringTidak

Tanggapan

NamaJenisWajibTentang apa ini
statestring<not_requested, pending, verified, rejected>Ya⛔ Four states, not a boolean. `not_requested` and `rejected` both refuse an order and the customer's next action differs completely: one is "tell us who you are", the other is "…
may_orderbooleanYaTrue only in `verified`. Read this rather than re-deriving it from `state`.
legal_namestringYaThe legal name of whoever is responsible for the machines.
countrystringYaISO-3166-1 alpha-2 country of the person or the incorporation.
company_numberstringYaCompany registration number, or `""` for an individual — a real answer.
abuse_contact_emailstringYaA monitored address an abuse report can be forwarded to and answered from. We are the account holder of record, so a complaint reaches us first and has to reach the customer wit…
intended_usestringYaWhat the customer says the machines are for, in their own words.
rejection_reasonstringYaShown to the customer **verbatim** when `state` is `rejected`.
submitted_atstringYa
reviewed_atstringYa

Kesalahan yang dapat dikembalikan oleh titik akhir ini

401 · 403 · 422 · 429