Clarification Needed on Scheduled Order Timing Fields
z
zyra
Hi ISN Support,
I'm currently working on integrating your API to surface available appointment windows and need clarification on interpreting scheduled job data returned from the Scheduled Orders endpoint.
Here’s a sample response we’re receiving:
json
{
"id": "3318725d-7a10-42d3-8341-12bfc9aaebf4",
"oid": 12963,
"address": "8140 Theisen, Center Line, MI 48015",
"datetime": "2025-07-14 07:00:00",
"duration": 30,
"created_datetime": "2025-07-14 09:55:31",
...
}
I need confirmation on the following:
Is the datetime field the actual start time of the scheduled order?
Is the duration field (e.g., 30) representing the job length in minutes?
Is this the correct way to determine the full time block of the scheduled job:
start_time = datetime and end_time = datetime + duration?
I’m working on building logic to suggest the best appointment time slots based on existing schedules, so understanding this is essential. If possible, a Loom video or brief explanation from your team showing how this reflects in the ISN UI would be really helpful.
Thanks in advance!
z
zyra
I need confirmation on the following:
Is the datetime field the actual start time of the scheduled order?
Is the duration field (e.g., 30) representing the job length in minutes?
Is this the correct way to determine the full time block of the scheduled job:
start_time = datetime and end_time = datetime + duration?
I’m working on building logic to suggest the best appointment time slots based on existing schedules, so understanding this is essential. If possible, a Loom video or brief explanation from your team showing how this reflects in the ISN UI would be really helpful.