Certification

"Certification" means two different things. We keep them apart.

Connection certification#

Every connection starts in certifying after you redeem its code. While it is certifying:

• listing writes are accepted and validated exactly as on an active connection, but every valid item answers needs_review and waits; invalid items answer rejected with pointers;
• nothing reaches the worker, and no item.* webhook fires for these needs_review items (the batch result already says it);
• removing an item that never went live removes it at once; reconcile only touches imported listings, of which a certifying connection has none.

Novi Kvadrat staff look at your batch: the mapped preview, the validation outcome and any likely duplicates of the agency's existing listings (they choose to link your item to an existing listing or create a new one). Then:

• Certify → the connection becomes active; everything waiting imports, honouring the link / create choices. Webhooks connection.status_changed (active) and, per item, item.imported (live) or item.validated (sandbox), then batch.completed. Your admins get an email.
• Send back with a note → the connection stays certifying; the waiting items turn failed with certification_rejected and the note; webhook connection.certification_rejected carries the note. Fix and push again: new pushes replace the failed items.

Each connection is certified once. After that, verified agencies go live at once and unverified agencies' listings wait for moderation — exactly as when the agency publishes in its own editor.

Partner certification#

Before you get a live app, you run the certification checklist on the sandbox: ping and signature failures, redeeming the test code, batches, updates, photos, states, removal, reconcile, webhooks, the validator, key rotation, and your live IP addresses. Then an admin presses Request live access — see Requesting live access.