a
aschroer
Hello ISN team,
Tennessee Home Inspectors (company key: tnhomeinspect) is requesting full API and webhook access for an internal operations system we are building with our technology partner, PivotNest Labs. ISN remains our system of record. This system sits alongside ISN to catch missed work, such as an order missing a provider, a blank fee field, missing access info, or a vendor report that hasn't been delivered yet. It does not replace any ISN function.
Third-party application:
THI Operations Control Center, an internal system built and maintained by PivotNest Labs for Tennessee Home Inspectors only. It is not a commercial product and not shared with other companies.
What the integration will accomplish:
  • A daily audit of scheduled orders: provider and inspector assignment, service fees populated, access information present.
  • Tracking of third-party specialty services (termite, radon, sewer scope) from order to report delivery.
  • Reconciling incoming email and order notes against ISN, so that changes like reschedules or new access instructions are caught.
  • Prompt alerts to our staff for unscheduled orders and urgent same-day issues, sent as text messages from THI's existing ISN texting number.
  • Entering property access information (lockbox, gate code, access type) that agents send us by email into the correct ISN order fields, after staff approval.
  • Later: two-way texting with agents and clients from our ISN number, for example inspectors updating arrival times.
Information exchanged:
  • Reading from ISN:
    orders, including services, fees, inspector assignments, custom order controls, notes, history and attachments; clients; agents; agencies; users; services and packages.
  • Writing to ISN, enabled gradually and only after testing and human approval:
    order notes, order attachments (vendor reports), selected custom order controls used for workflow status, and order access fields (lockbox, gate code, access type).
  • Sending through ISN:
    text messages from THI's ISN texting number, to our team members first and to agents and clients later.
When:
  • Webhooks in real time.
  • Polling with the
    after
    filter every 15 minutes as a safety net.
  • A full reconciliation several times per business day.
How it helps our business:
fewer missed vendor reports, fewer orders missing providers or access information, faster response to new inquiries, and a clear audit trail of every action.
Security:
  • A dedicated ISN service user, not a personal login.
  • Credentials kept in an encrypted secrets store and never in code.
  • Webhook signatures verified (HMAC).
  • All access logged.
  • Lockbox and access codes excluded from logs and AI processing, stored encrypted only until they're entered into ISN, and visible only to staff who need them.
## Specific access we're requesting
  1. API access keys enabled
    for a dedicated service user with read access across all orders, not limited to one inspector's orders.
  2. Webhooks enabled
    for all available order events: created, scheduled, updated, datetime, status changed, assignment changed, paid, signed, completed, note created/updated/deleted.
  3. Write access
    for order notes, order attachment upload, custom order controls (
    controls
    /
    controls-v2
    ), and order access fields (lockbox, gate code, access type).
  4. Order files:
    read access to the attachments list (
    /orderfiles
    ), plus, if possible, a way to list the attachments on a single order.
  5. Text messaging:
    API access to send texts from THI's ISN texting number, to team members now and to agents and clients later.
## Questions: capabilities we need that aren't in the public API docs
We'd appreciate either access or a recommended supported approach for each:
  1. Inspection Grid Flags:
    can flag states be read or set through the API? If not, is it on the roadmap?
  2. Report and attachment delivery:
    can we trigger ISN's normal delivery of an uploaded attachment to the client and agent through the API? Or can we read delivery history to confirm what was sent?
  3. Tasks:
    is there an API to read, create and complete Tasks? We see Create and Complete through Zapier, but we need to read existing tasks to avoid duplicates.
  4. SMS:
    can we send texts from our ISN texting number through the API, to staff and inspectors now and to agents and clients later? Replies currently reach us as emails. Is there an API or webhook for incoming replies, so we can connect each reply to the right order and conversation?
  5. Unscheduled orders and inquiries:
    what is the supported way to list unscheduled or draft orders?
  6. Additional webhook events:
    are events available for attachments, custom controls or tasks?
  7. Order notes:
    how are notes created through the API attributed? Can they show as coming from our service user or a named system?
  8. Access fields:
    do lockbox, access type and gate code come back on order reads? We'd like to write them through
    POST /order/{id}
    and then read them back to confirm the update. Which fields should we use for a lockbox code versus a gate or door code?
  9. Test environment:
    can ISN provide a sandbox or test company so we can test writes without touching live orders?
  10. Automation policy:
    for functions with no API, would ISN permit limited, logged, authenticated browser automation by our service user? We don't plan to do this without written permission, per your Terms of Service.
  11. MCP:
    what is the monthly tool-call allowance for our company?
Thank you. We're glad to get on a call if that's easier.
Aaron Schroer
Owner, Tennessee Home Inspectors
615-545-5660 tnhomeinspectors@gmail.com
isn-integration-request

isn-integration-request