Skip to content

Validation ​

We check your implementation in two ways, and show the results to the organiser in Innercrowd, down to the field involved.

Full validation, when the organiser first connects and whenever your capabilities change: one is added or removed, or its version or options change. We test every capability you advertise (or every one that changed) against the contract: /v1/account, the first page of /v1/events and /v1/orders, GET /v1/orders/{id} with webhooks, and a test voucher that we delete straight away with vouchers. Problems with the account or with the shape of a page block the connection. A single record that breaks the contract is only a warning: it is skipped, and the rest comes through.

Daily health check against /v1/account: does the key still work, and did your capabilities or their options change? We pick up changed options, such as a new rate limit, straight away, and run the full validation for capabilities that changed.

To compare your output with a working example, a reference implementation of the contract with a public demo key will be published together with the API documentation. The OpenAPI 3.1 document follows with the API reference.

Example report ​

CheckResultDetails
/v1/accountPassThe Crave (TicketCo)
/v1/eventsPass3 events on the first page
/v1/ordersWarning1 record will be skipped: ord_993 · items.0.product.price.currency: The currency field is required.
/v1/vouchersPassCreated and deleted a test voucher
/v1/orders/{id}Passord_991 matches its record in /v1/orders