GET policy details returns HTTP 500 for one iOS policy in Hexnode APISolved

Participant
Discussion
2 months ago Oct 04, 2026

One iOS policy in our portal consistently fails when fetched through the Hexnode REST API. The list endpoint works and shows the policy metadata, but GET /api/v1/policy// returns HTTP 500 every time with an “unexpected condition” message.

Other policies return 200 using the same API key, including policies with passcode rules, restrictions, Exchange ActiveSync, Wi-Fi, app management, kiosk settings, and wallpapers. The affected policy still opens in the web console, saves correctly, and pushes to devices. It includes Extensible SSO and a custom configuration profile, so I’m trying to narrow down whether one of those payloads is causing the policy detail response to fail.

Replies (1)

Marked SolutionPending Review
Hexnode Expert
2 months ago Oct 04, 2026
Marked SolutionPending Review

Hi @verbnigge,

This behavior points to an issue in the policy detail serialization path rather than an authentication or endpoint usage problem, especially if:

– GET /api/v1/policy/ lists the policy successfully.
– Other policy detail endpoints return 200 OK with the same API key.
– The affected policy can still be edited and deployed from the Hexnode console.

A useful way to isolate the trigger is to compare the affected policy with test policies:

  1. Create a new policy with only the suspected payload, such as Extensible SSO, and test GET /api/v1/policy//.
  2. Rebuild the full policy manually with the same visible configuration and test the API response.
  3. Clone the affected policy from the console and test the cloned policy’s detail endpoint.

If the manually rebuilt policy returns 200 OK but the cloned policy also returns HTTP 500, the issue is likely tied to stored payload data copied from the original policy rather than the visible configuration itself.

Regards,
Sienna Carter
Hexnode UEM

Save