Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support email_ccs property at create ticket api #309

Open
staust opened this issue Mar 7, 2024 · 0 comments
Open

Add support email_ccs property at create ticket api #309

staust opened this issue Mar 7, 2024 · 0 comments

Comments

@staust
Copy link

staust commented Mar 7, 2024

It would be nice to add support for email_ccs property at create ticket api endpoint.
https://developer.zendesk.com/documentation/ticketing/managing-tickets/creating-and-updating-tickets/#setting-email-ccs

Currently only email_cc_ids is supported which requires to be known users to zendesk. With the email_ccs property it is possible to add unknown/new email contacts to tickets which is especially useful for out bound contacts, like in their example:

{
  "ticket": {
    "email_ccs": [
      { "user_id": "562624", "action": "put" },
      { "user_id": "243642": "action": "delete" },
      { "user_email": "else@example.com", "user_name": "Someone Else", "action": "put"}
    ]
  }
}

The current workaround is to use the generic POST capability of the library to create tickets including those properties.

@staust staust changed the title Add support for setting generig email ccs Add support for setting email_ccs property on create ticket api Mar 7, 2024
@staust staust changed the title Add support for setting email_ccs property on create ticket api Add support email_ccs property on create ticket api Mar 7, 2024
@staust staust changed the title Add support email_ccs property on create ticket api Add support email_ccs property at create ticket api Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant