Questions regarding Batch Validation endpoint

STRR
1

Booking.com has some questions regarding the proposed batch validation endpoint in the STRR API

  1. Is there a way to guarantee that we will have a result returned immediately? providing a callback URL that is accessible over the public internet is not simple (e.g. auth and security concerns) and immediate results are much preferable to us to fit in with our current validation architecture. Eventually we can move away from requiring batch validation, but that is not feasible before H2 at the earliest.
  2. In the schema we’ve seen, there’s no response body schema. Is it possible to share this schema, and if its different, what the request body of the callback will look like?
  3. Is the callback URL paradigm guaranteed or is it liable to change?
2

@spencer.gervais Thanks for reaching out with your questions!

I’ve connected with our technical architect, and you’ll find their responses below. Let me know if you need any further clarification.

  1. No, some of the requests are too large, hence using an OAS callback. The requirement is to submit the entire set everyday, and for some groups that’s in the 10s of thousands. We suggest you putting some key identifier into your callback.
  2. We’ll check and ensure the spec is posting properly.
  3. It’s not going to materially change. In discussion we’re looking at have the base domain added into the registration, but this would not change the callback specification, just rather confine the domain the callback URI can use.