Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I’m having an issue accessing one of my interfaces. It keeps on showing error 500 | Uh oh, something went wrong. `Unexpected token '<', "<!DOCTYPE "... is not valid JSON`.

Though I have no issue accessing my other interfaces.

 

 

New error showed up when I tried accessing it again (500 | Uh oh, something went wrong. JSON.parse: unexpected character at line 1 column 1 of the JSON data)

 

 

Hi there @hanvergs,

Welcome to the Community! 🎉

Due to our limited resources regarding Interfaces. I’d recommend reaching out to our Interfaces Support Team regarding this issue.

You can reach our Interfaces team here: https://eap.zapier.app/interfaces

Hopefully, this helps.

Dear @hanvergs,

 

 

It seems you might either be making the API call to the wrong route, or perhaps your configurations are not quite right, causing this kind of error:

**"Error 500 | Uh oh, something went wrong. `Unexpected token '<', "<!DOCTYPE "... is not valid JSON`.**"

 

I’d suggest using PostMan to debug the API call in an isolated environment.

Here’s a quick guide:

 

- Setting Up Postman:

    - Ensure Postman is installed and set up correctly on your system.

    - Create a new environment in Postman. (This will help you manage your secret keys variables. )

    - Create a new request in Postman to the interface causing the error.

 

- Replicating the Issue:

    - Input the URL of the problematic interface.

    - Set the appropriate HTTP method (GET, POST, etc.).

    - Add headers and body data if required.

 

- Analyzing the Response:

    - Send the request and observe the response.

    - Check if the response body contains HTML (indicated by `<!DOCTYPE`) instead of expected JSON format.

 

- Investigating the Error:

    - If an HTML response is received, it often indicates a server-side error.

    - The server might be misconfigured or encountering an internal issue.

 

- Comparing with Functional Interfaces:

    - Send requests to the interfaces that are working correctly.

    - Compare their request setup (headers, body, etc.) with the problematic one.

    - Try different options like (form-data, raw, GraphQL, etc), depending on your configuration.

 

- Checking Server Logs:

    - If possible, access the server logs to identify any internal server errors causing the 500 response.

 

- Consulting Server/Backend Team:

    - If the issue persists, consult with your server or backend team with the details from Postman.

 


 

Best Regards,

Dillon Breytenbach @ DashSquared Team

Reply


Terms & Conditions