Recent searches


No recent searches

/account/settings.json mostly unmodifiable



Posted Aug 17, 2021

Most of the data inside of account settings is unmodifiable via API, which is the opposite of what is stated within the API reference.  Is this known?
 
Response when attempting to update settings:
 
X-Zendesk-API-WarnRemoved Params: Unpermitted parameter keys: '["settings.apps.use", "settings.apps.create_private", "settings.apps.create_public", "settings.apps", "settings.tickets.collaboration", "settings.tickets.agent_collision", "settings.tickets.maximum_personal_views_to_list", "settings.tickets.status_hold", "settings.tickets.rich_text_comments", "settings.tickets.assign_tickets_upon_solve", "settings.tickets.allow_group_reset", "settings.tickets.using_skill_based_routing", "settings.chat.enabled", "settings.chat.integrated", "settings.chat.available", "settings.chat.maximum_request_count", "settings.chat.welcome_message", "settings.chat", "settings.voice.enabled", "settings.voice.logging", "settings.voice.outbound_enabled", "settings.voice.agent_confirmation_when_forwarding", "settings.voice.agent_wrap_up_after_calls", "settings.voice.maximum_queue_size", "settings.voice.maximum_queue_wait_time", "settings.voice.only_during_business_hours", "settings.voice.recordings_public", "settings.voice.uk_mobile_forwarding", "settings.voice", "settings.twitter.shorten_url", "settings.twitter", "settings.user.time_zone_selection", "settings.user.language_selection", "settings.user.multiple_organizations", "settings.screencast.enabled_for_tickets", "settings.screencast.host", "settings.screencast.tickets_recorder_id", "settings.screencast", "settings.gooddata_advanced_analytics.enabled", "settings.gooddata_advanced_analytics", "settings.statistics.forum", "settings.statistics.search", "settings.statistics.rule_usage", "settings.statistics", "settings.active_features.on_hold_status", "settings.active_features.topic_suggestion", "settings.active_features.voice", "settings.active_features.facebook_login", "settings.active_features.google_login", "settings.active_features.twitter_login", "settings.active_features.forum_analytics", "settings.active_features.agent_forwarding", "settings.active_features.chat", "settings.active_features.chat_about_my_ticket", "settings.active_features.satisfaction_prediction", "settings.active_features.csat_reason_code", "settings.active_features.screencasts", "settings.active_features.markdown", "settings.active_features.bcc_archiving", "settings.active_features.advanced_analytics", "settings.active_features.insights", "settings.active_features.explore", "settings.active_features.explore_on_support_ent_plan", "settings.active_features.explore_on_support_pro_plan", "settings.active_features.good_data_and_explore", "settings.active_features.good_data_only", "settings.active_features.explore_forbidden", "settings.active_features.explore_not_set", "settings.active_features.sandbox", "settings.active_features.suspended_ticket_notification", "settings.active_features.twitter", "settings.active_features.facebook", "settings.active_features.dynamic_contents", "settings.active_features.light_agents", "settings.active_features.ticket_forms", "settings.active_features.user_org_fields", "settings.active_features.is_abusive", "settings.active_features.rich_content_in_emails", "settings.active_features.benchmark_opt_out", "settings.active_features.fallback_composer", "settings.ticket_form.raw_ticket_forms_instructions", "settings.rule.using_skill_based_routing", "settings.metrics.account_size", "settings.metrics", "settings.ticket_sharing_partners.support_addresses", "settings.ticket_sharing_partners"]'.

0

2

2 comments

image avatar

Tipene Hughes

Zendesk Developer Advocacy

Hi @...,

Would you be able to provide an example of the payload you're sending with the request? Just be sure to redact any sensitive info.

Thanks!

Tipene

0


image avatar

Tipene Hughes

Zendesk Developer Advocacy

I’ve looked a bit further in to this issue and it appears that the unpermitted parameter keys present in the response you received are read-only fields and cannot be modified via the API. At this stage, only the properties present in the documentation with a read-only status of no can be modified via the API.

I can understand how this could lead to confusion - especially if you were to make a GET request to the account/settings endpoint and the make changes based on the result you had received. I’ll be raising this with our documentation team to see how we can make this clearer, moving forward. In the meantime, you can still refer to the documentation to determine which fields are able to be modified via the API.

I hope this helps! Feel free to reach out if you have any further questions.

Tipene

-1


Please sign in to leave a comment.

Didn't find what you're looking for?

New post