Bulk delete triggers API

Hey @victor14

I'm not much with curl but have you tried using Postman (you can use it for free) to run your API commands with Zendesk?

The best part is all the Support endpoints can be downloaded and 'uploaded' in postman as a collection...then you just set your authorisation and you have a very easy to work with tool on the Zendesk APIs.

When setting your authorisation for a Zendesk endpoint, use:

Type: Basic Auth
Username: {your email address}/token
Password: Your API token

I'd recommend using variables for these so it remains more secure across your Postman account.

I recommend to give it a go. Here is a little self made tutorial to maybe get you started. This page on Exploring the Zendesk API with postman is also great.

Hi @chad16

I also tried with Postman. Below you can find the evidence:

• Get all triggers using an authentication token. (The response is successful)

• Delete a trigger using the API (The response is successful)

• Delete a trigger that doesn't exist using the "Delete in bulk" API. Returns a 404 error that indicates that the record is not found. (The response is successful)

• Delete an existing trigger using the "Delete in bulk" API. This is the issue that we're facing. (Returns a 400 error)

I hope you can help me on this.

Hi @chad16, do you have any suggestions to solve the issue?

Hi Victor! Just a shot in the dark, since I have actually seen this cause issues in the past, could you append `.json` to `destroy_many` so that your url is `.../api/v2/triggers/destroy_many.json?ids=...`

I'm not sure why, but this has resolved similar issues, so it's worth a shot. Let me know if that works!

Hi @greg29, thanks for your response.

But it didn't worked :(

I also tried to do the authentication with username/token and the API token, using the without and with the .json, but it also fails.

Do you have any other suggestion?

Thanks for your help.

Hi @victor14

That error looks like an authentication error. Are you sure you have the correct credentials?

Also, when bulk deleting triggers, make sure the triggers you want to delete are deactivated first.

I tried my instance and bulk delete worked fine but the triggers had to be deactivated first. Also, the response is '204 no content'. The endpoint works but it just doesn't return any content.

Hi @chad16

You're right! I need to deactivate all the triggers to be able to delete them in bulk! I was confused because the deleteTrigger API is able to delete the trigger even if it is active.

Thanks for your help!

@chad16

Just a query:

Why the DELETE trigger API (/api/v2/triggers/{trigger_id}) allows to delete an active trigger & DELETE bulk triggers (/api/v2/triggers/destroy_many?ids={ids}) doesn't?

Hi @victor14 - That's great. Happy to help.

As for the different endpoints deleting and not deleting active triggers - good question. I have no idea. I think one of the API team would be best placed to answer this. On the surface it seems a bit weird that one will delete active triggers and the other doesn't.

Cheers
Chad