February 2025 Updates

🆕 Support for Assignment Conflict check - Create Job and Assign User to Job API now supports a new query param check_assignment_conflict which will mandate the API for the users to be assigned has any other jobs conflicting with this job's scheduled_start_time & scheduled_end_time.

If you send this param as true and the user has any other job conflicts, you will receive HTTP error code 409 along with the list of users & job who have assignment conflicts.

Note: This param only works for individual job creation & assignment and is not enabled for bulk action or data import API.

🆕 New low_stock key in Products - We have added a new Boolean flag low_stock in Product listing and details API. If the item has track_quantity set to true and the item goes below configured threshold quantity, Zuper will automatically toggle this key to true, this helps you to identify any items that are running low on stock. This flag has also been added as a filter in GET products API to let you filter only items that are running low on stock.

⭐ Support for team_uid in Create User - We have made it easier for you to assign one or multiple teams to user in the new user creation API call. You can now send an array of team_uid inside the key team_uid of the user object payload. Note: This API only supports sending up to 10 team_uid at a time.

⭐ Support default_product_location in Create User - You can now send the default warehouse location of the user inside the default_product_location key under meta_data. If the default warehouse location is set, Zuper mobile app will automatically choose this location when the technician is adding items to the job.

⭐ Support for filtering teams by skillset_uid - We have improved the GET teams API to support filtering teams who has user possessing one or more skillsets. You can pass the skillsets required inside filter.skillset_uid which will automatically return only teams who has users with the skillsets sent.

⭐ Improvement in New Recurring Job - We have made an improvement in create recurring job API which will create 5 jobs upfront and the rest of the jobs in the recurring job instances are created in the background for a faster response in the creation API.

🐞 Daylight savings fix in Assisted Scheduling API - We have made a minor fix in Assisted scheduling API where the API was missing the first slot on the day when the daylight savings start.

🐞 triggered_by user now sent in New Job - We have fixed a minor bug where the triggered_by user key was not sent in the webhook payload if the job was created through workflow automation.