Redirect API | Community
Skip to main content

Redirect API

  • May 16, 2024
  • 2 replies
  • 0 views

Jenna14

I'm getting 403 errors when trying to do a simple redirect. It's not an authorization or authentication issue.  Zendesk Support has done troubleshooting and finally told me to post here. I understand this basic maintenance feature is still in EAP, so perhaps this is expected behavior.  Our customers are getting 404 responses on deleted/archived articles. Really hoping someone can suggest a workaround to compensate for the non-functioning of the Redirect API that can buy us some time and make our customers' experience less terrible. Also, does anyone have a ballpark timeline for when this is expected to work (1-6 months, longer)? Thanks.

Endpoint: POST /api/v2/guide/redirect_rules
Body: {

"redirect_rule": {

"redirect_from": "/hc/en-us/articles/243512266. . .",

"redirect_status": "301",

"redirect_to": "https://../hc/en-us/articles/243914636. . ."

}

2 replies

Greg29
  • May 16, 2024

Hi Jenna! I took a look at the ticket that you had opened, as well as looking around internally and I don't have a good answer for you at the moment. With this being an EAP (early access program), we have limited understanding of expected functionality. That being said, I reached out to the person running the EAP and I'll see if we can't find a resolution for you. They're in a different time zone, so I might not hear back immediately, but as soon as I know more, I'll drop you a line!


Ryan48
  • May 17, 2024

Hey Jenna,

 

I just looked through your account config to troubleshoot this. I can see you've created a set of redirects for URLs that are not articles that are working just fine. The Redirects API was built for exactly this situation and is working for other customers. The 403 error tells me there is an auth issue. 

I'm going to raise a ticket for you and I to troubleshoot this direclty. 

Thanks!