Skip to main content
Contributor I
April 19, 2026
Solved

500 Internal Server Error when activating draft object schema via Update Object Schema API

We already have an active schema for the object type and are trying to create and activate a new schema version.

Steps:

  1. Existing active schema is in use
  2. Created a new draft schema (POST /api/object-schemas)
  3. Configured properties and source mapping successfully
  4. Attempted to activate the draft schema using:

     

    PATCH /api/object-schemas/{id}

    with status = ACTIVE

Result: API returns 500 Internal Server Error
Expected: Draft schema should be activated and replace the current schema

 

Byrne C
Byrne CAnswer
Community Manager
April 20, 2026

Hi ​@hiennguyen.consultinghnl,

Thank you for alerting us of this 500 error! I just let our APIs team know about this, and will update once I have more information!

1 reply

Byrne C
Community Manager
Byrne CAnswer
Community Manager
April 20, 2026

Hi ​@hiennguyen.consultinghnl,

Thank you for alerting us of this 500 error! I just let our APIs team know about this, and will update once I have more information!