Tweet
Hello,
I’m experiencing an issue when calling the metadata API.
I use a script that reads metadata via the API, extracts the option values from enum/multienum fields, and stores them in a JSON file. The script itself does not apply any filtering, sorting, or transformation beyond what is returned by the API.
Since 06/03/2026, I have started receiving a JSON response with a different structure and different fields compared to what the API previously returned.
I have attached screenshots showing the previous JSON response and the current one for comparison.
Could you please confirm whether this change is due to a temporary issue or if the metadata API response format has been officially modified and will remain like this going forward?
Thank you in advance for your help.
I’m experiencing an issue when calling the metadata API.
I use a script that reads metadata via the API, extracts the option values from enum/multienum fields, and stores them in a JSON file. The script itself does not apply any filtering, sorting, or transformation beyond what is returned by the API.
Since 06/03/2026, I have started receiving a JSON response with a different structure and different fields compared to what the API previously returned.
I have attached screenshots showing the previous JSON response and the current one for comparison.
Could you please confirm whether this change is due to a temporary issue or if the metadata API response format has been officially modified and will remain like this going forward?
Thank you in advance for your help.
Attached Files
Comment