ISN API Documentation
in review
L
Lindsay G - ISN Product
Merged in a post:
Integration with 3rd party apps via API
p
pheller
I am trying to utilize the ISN API to access my ISN from another platform (n8n.io) Can our account at goisn.net be given access to the modern v1 or v2 REST API, like the one documented at api.inspectionsupport.net? We want to build an integration and use modern, documented endpoints.
We must use the goisn.net/sdinspect/rest endpoint for our integration. Please provide the complete developer documentation for this specific endpoint, including the list of all valid action names and their required parameters.
The only iteration for which you provide documentation is Zapier. We need access from other platforms. Thank you! Philippe Heller, The Real Estate Inspection Company
L
Lindsay G - ISN Product
Merged in a post:
API Request
T
Tommy
I am making an app and need API access so that users can look at their most recent jobs and automatically fill in job descriptions from the API pull.
L
Lindsay G - ISN Product
Merged in a post:
API calls potential issue.
p
pheller
We are building an integration using the v1 OpenAPI documentation you provided.
When we send a GET request to our correct v1 endpoint (https://goisn.net/sdinspect/json/calendar/availableslots), your server is incorrectly responding with an error message from your old API: {"message":"missing or invalid action specified"}.
This indicates our account has not been correctly configured to use the v1 API endpoints. The server appears to be routing our v1 calls to the old system.
Please can you ensure our account is correctly configured to use the v1 REST API at the /json path, as per your documentation?
Your ISN account is set up under the 4isn.com domain, so your API calls usually need to use endpoints on that same domain. If you’re using other domains like goisn.net or api.inspectionsupport.net, you might get authentication errors or messages like "missing or invalid action specified" because your credentials won’t be recognized across different domains.
What to try:
Use 4isn.com as the base URL for all API requests.
Ensure your API key or token is used only with this domain.
ISN has two APIs: one to access all ISNs, and one to access a single ISN once you know the company key. Since you already have your company key, you probably don’t need to use the Admin API—you can just connect directly to your ISN.
How it usually works:
You put together your REST URL like this: your domain + your company key + /rest
For example:
(where 4isn.com is your domain and yourcompany is your company key).
I’m not an expert on ISN’s API, but this is just my suggestion to try and might help fix the issue. It may or may not solve it, but it’s worth a shot.
We’ve tried just about every combination we can think of. Various domains, /rest/ vs. /json/ etc.
But the results are simply wrong. For example when we try to get a report, or search for one agent
Ex: https://goisn.net/sdinspect/json/agents/search?q=Anderson we get a list of all of our agents. This example comes directly from the api.inspectionsupport.net website. This is the same when we look for a report. We get all 70,000 reports back.
Our simple goal is just to get the availability endpoint /calendar/availableslots to work and it fails no matter what we do. We just get an error whether we use REST or JSON:
{
"status": "error",
"message": "missing or invalid action specified"
}
Do you have any companies successfully using these api endpoints? It might be a very simple solution. Our ISN has been in place a long time. Is there something in our setup interfering with the API calls?
L
Lindsay G - ISN Product
marked this post as
in review
Alfredo Ruiz Perez
These guys are never coming back at you with a solution but I got your back. I found through trial and error and tears that to get the slots you need to GET
https://goisn.net/sdinspect/rest/availableslots?inspector={your_inspector_uuid}&daysahead={days_after_today}&offset={how_many_days_in_advance}&services={sevice_1_uuuid},{service_2_uuid},{service_3_uuid}&zip={zip_code}
I'm happy to help if you need clarification or any other problems as long as I've deciphered the mess this company has for an api,
Cheers
p
pheller
Alfredo Ruiz Perez I'm sorry for the slow reply! Yes, it is maddening how poorly they respond, and the documentation is a mess. I have spent days and days trying to get this to work. I finally did and your input was instrumental.
This is for a voice agent to be able to give availability. Next step - holding a time slot. Have you tackled that yet?
Janaya Fix - Product Management
Hey Tommy, thanks for your feedback! I have a few more questions for you:
- What specific data points or information do you need from the API to support your app's functionality?
- How frequently do you anticipate needing to access the API for updates on job statuses or descriptions?
- Are there any specific security or authentication requirements you have for accessing the API?
T
Tommy
Janaya Fix - Product Management
- What specific data points or information do you need from the API to support your app's functionality?
I need access to the Jobs (Inspections) endpoint to retrieve data such as:
Client Name
Property Address
Inspection Date and Time
Inspector Name
Job Status (e.g., Scheduled, Completed)
Services Ordered (optional)
Later, I may also want to pull company profile settings (optional) to display contact info, but initially it’s focused on inspections/jobs.
- How frequently do you anticipate needing to access the API for updates on job statuses or descriptions?
I anticipate accessing the API in two main ways:
On user login to sync any upcoming inspections.
Once or twice per hour while the app is open to refresh inspection status (optional).
I do not expect high-frequency polling (e.g., no need for updates every few seconds or minutes).
- Are there any specific security or authentication requirements you have for accessing the API?
I prefer using OAuth 2.0 Authorization Code Flow for security, so that users can log into ISN directly from the app, and I can retrieve an access token securely.
I would like:
Long-lived Refresh Tokens (if possible)
Scoped Access limited to necessary endpoints (Jobs/Inspections, not billing or user management)
HTTPS-only communication