Session Priority Endpoint Status Code Update

Endpoint Affected:

sessions_setpriority: POST /sessions/{id}/priority

Zaptec has updated the /sessions/{id}/priority endpoint to improve error handling for requests missing a body. Previously, if the request body was missing, the endpoint returned an HTTP 500 (Internal Server Error). With this change, the endpoint will now return an HTTP 400 (Bad Request) status code instead.

This update ensures more accurate status reporting, aligns with RESTful API conventions, and helps integrators diagnose issues more effectively.

Impacted Behavior

Required Integration Changes

1. Update Error Handling Logic

Integrators should update their client applications to expect a 400 status code (instead of 500) when the request body is missing for this endpoint. Ensure that error handling and logging are adjusted accordingly.

2. Review API Usage

Double-check that all requests to /sessions/{id}/priority include the required body to avoid receiving a 400 response.

Next Steps

• Update your integration to handle the new 400 response.
• Review your API client code to ensure all requests to this endpoint include the necessary body.
• Monitor for 400 responses and adjust error diagnostics as needed.

For further details, see the Zaptec API Reference.