PricingBlog

API error endpoint changed from msg to message?

  • uunicode-1410270273843888240

    unicodes

    6 months ago

    The "end point" for api's errors message has been changed from msg to message or some API return in msg and other in messages?

    Thank you.
  • andreasmoller-1410275179929538670

    Andreas Møller

    6 months ago

    I don't think I follow.

    What end point?
  • uunicode-1410275519995449527

    unicodes

    6 months ago

    I don't know if depends of API service, but before the errors was returned in API > error > msg. Not is API > error > messages.
  • I was thinking if this changed, the old apps that was using msg, still gets the content of API error message or should be updated from msg to message.
  • 1410275919821799495-Screenshot_2025-08-27_at_17.52.55.png
  • andreasmoller-1410275973227741286

    Andreas Møller

    6 months ago

    I think we just set the error property, i believe that anything under that is the API
  • uunicode-1410275988964774099

    unicodes

    6 months ago

    Now is null, but when you get errors it returns some data.
  • andreasmoller-1410276555229233283

    Andreas Møller

    6 months ago

    Check the Network tab. I am pretty sure we return the error the same way we receive it
  • uunicode-1410276886038184057

    unicodes

    6 months ago

    I was always used supabase and in this period i'm noticing that the error message isn't anymore returned in msg but in message. Before that message was "msg"
    1410276885824405624-Screenshot_2025-08-27_at_17.56.37.png
  • lucasg-1410288515626831973

    Lucas G

    6 months ago

    I don’t recall this myself but it should be message either way
  • The standard way to access it
  • andreasmoller-1410288832817008721

    Andreas Møller

    6 months ago

    It depends on the API.
  • lucasg-1410290193197699207

    Lucas G

    6 months ago

    True standard is not the correct word. “Common