Domo encountered an error proxying your request: 500

User_32236
User_32236 Member
in APIs & Domo Developer

I have an API running in postman successfully, but when I am trying to perform the same using DOMO custom connector it gives the below error.

Domo encountered an error proxying your request: 500

Can someone through some light on this? not sure what this error means, Where I can get the full details of error logs?

Answers

  • GrantSmith
    GrantSmith Coach

    Hi @User_32236

    500 (see https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/500) simply means an internal server error (essentially Domo had an issue processing your API request). It's an HTTP response code. Typically when I've seen 500 error in the past it's because of malformed data being sent to the API call. Have you confirmed you're sending the same data via postman and via your custom connector script in the same package / envelope / format?

    **Was this post helpful? Click Agree or Like below**
    **Did this solve your problem? Accept it as a solution!**
  • jaeW_at_Onyx
    jaeW_at_Onyx Coach

    @User_32236 ,

    Are you hitting a Domo internal API or an external API? Domo has restrictions on which internal APIs can be hit.

    For more details on the error you can email support@domo.com and they'll forward your issue to the connectors team.

    Alternatively there is a Connector Support email <supportconnectors@domo.com>

    Jae Wilson
    Check out my 🎥 Domo Training YouTube Channel 👨‍💻

    **Say "Thanks" by clicking the ❤️ in the post that helped you.
    **Please mark the post that solves your problem by clicking on "Accept as Solution"
  • User_32236
    User_32236 Member

    @jaeW_at_Onyx ,

    this is external API(Qualtrics Survey results).

    Yes I have started discussing with DOMO support team on this issue.

  • User_32236
    User_32236 Member

    @GrantSmith,

    Yes I am using same API with same parameters, I thought it could be because of the limitations(API response is >50MB) displaying in IDE.

    I see same same error even after publishing the custom connector.

Categories