zendesk_api_client_rb icon indicating copy to clipboard operation
zendesk_api_client_rb copied to clipboard

Official Ruby Zendesk API Client

Results 39 zendesk_api_client_rb issues
Sort by recently updated
recently updated
newest added

Hi there? Is there any existing plan or work being done to support attachment management workflows in this library? (ie. to redact/remove attachments - https://developer.zendesk.com/api-reference/ticketing/tickets/ticket-attachments/#redact-comment-attachment)

While attempting to merge 2 users together in Zendesk, I received a 422 response with the response body `{"error"=>"You cannot merge Customer Name while they have an external ID."}`. However,...

[See](https://developer.zendesk.com/api-reference/agent-availability/introduction/)

Small PR to remove the duplicate method named `self.new_from_response`. The class method already exists [here](https://github.com/zendesk/zendesk_api_client_rb/blob/master/lib/zendesk_api/resource.rb#L43#L50). Risk: Low

It seems like the side load behaviors of the `ZendeskAPI::Association` class could be encapsulated in a separate object for extendability so I thought it might be a good opportunity to...

https://developer.zendesk.com/api-reference/ticketing/targets/target_failures/#show-target-failure

it would be useful to have https://developer.zendesk.com/api-reference/ticketing/targets/target_failures/ ```ruby > Zendesk::Connection.client.target_failures Traceback (most recent call last): 1: from (irb):39 RuntimeError (Resource for target_failures does not exist) ```

Docs: https://developer.zendesk.com/api-reference/ticketing/introduction/#idempotency With the current API client, there doesn't seem to be a way to specify an idempotent key on specific requests

feature

According to [this announcement](https://support.zendesk.com/hc/en-us/articles/7386291855386-Announcing-the-deprecation-of-password-access-for-APIs) the password access to the API is being deprecated. The `README.md` file still lists this an a possible configuration option with no further comment. I was...