We are developing a new internal integration for Real Estate Inspections. ISN will remain the system of record, and our goal is to use ISN webhooks and the API to synchronize inspection scheduling information into an internal scheduling display.

We are not troubleshooting an existing integration, and we are not currently planning to write scheduling changes back into ISN.

We have reviewed the current developer documentation and would appreciate clarification from the Development team on the following items:

For GET /orders?after=<datetime>, what exactly does after filter on? Is it based on the order modified timestamp, and what timezone/format and inclusive/exclusive behavior should we use?

Are canceled orders still retrievable through GET /order/{id} and GET /orders?

Are deleted orders still retrievable, and is deletion soft or hard?

How does paging work for GET /orders on larger datasets? Are there page-size or response-size limits?

For tracked webhooks, what happens after the final retry attempt fails? Is there any replay capability, alerting, or automatic disabling?

Is there a sandbox or test tenant available for API and webhook integration testing?

Does an in-house integration used only by our own company require formal review or approval before production use?

Can API access keys be restricted to read-only scope, or do they inherit the full permissions of the ISN user who creates them?

Our intended architecture is:

ISN webhook → secure AWS endpoint → queue → worker → fetch current order from ISN API → update internal scheduling system

We will use the ISN Order ID as the synchronization key and will re-fetch the order from the API after relevant webhook events so ISN remains authoritative.

Thank you for any technical guidance you can provide.

Pete Ciliberto

Real Estate Inspections