Skip to main content
Answered

500 Error on get-tags-from-item endpoint

  • January 17, 2025
  • 3 replies
  • 95 views
Y
Forum|alt.badge.img+1

Hi!

 

it appears the https://developers.miro.com/reference/get-tags-from-item API endpoint is returning 500 errors.

Is there anything wrong with this endpoint ?

 

Here’s what I know so far:

  • items of payload are all sticky-notes
  • Sending the API request directly from the reference site does not result in an error.
  • 'x-request-id': 'c54a8c26-8334-4901-869c-5de2a22dc7fc'

  • The error response data is as follows:

{
  "type": "error",
  "code": "3.0016",
  "context": [Object],
  "message": "Internal error occurred",
  "status": 500
}

 

Thanks!

Best answer by Yushin

​@William Bishop Thank you for your response.

Upon further investigation, I’ve identified that the issue is likely caused by sending a large number of simultaneous requests to the Miro API at once.

In this case, I was using Axios in a Node application to send requests for multiple items’ tag information via the map() API. However, since I was processing hundreds of items concurrently in asynchronous operations, it appears that the Miro API was overwhelmed by the volume of requests, resulting in the 500 errors.

According to Miro’s rate-limiting documentation, exceeding the rate limit should typically return a 429 status code. However, in this situation, there was no rate limit credit exhaustion. I suspect the error was simply due to the excessive load within a very short timeframe.

3 replies

William Bishop
Mironeer
Forum|alt.badge.img+4
  • William Bishop
  • Mironeer
  • 248 replies
  • January 17, 2025

Hi ​@Yushin,

Thanks for reaching out! I’ve just tested this endpoint with tags on both sticky notes and cards, and I haven’t been able to reproduce this. I’ve tested with a cURL request, from Postman, and in our docs directly, but I don’t see any 500 errors. 

How are you sending the request? Have you tried copying sample code directly from our docs into your script or app? 500 errors can sometimes be misleading, I might suggest double checking your ids, params, etc. and make sure there’s nothing in your code that could be affecting the request since it’s working from the embedded request sandbox in our docs.

Y
Forum|alt.badge.img+1
  • Yushin
  • Author
  • New Here
  • 1 reply
  • Answer
  • January 20, 2025

​@William Bishop Thank you for your response.

Upon further investigation, I’ve identified that the issue is likely caused by sending a large number of simultaneous requests to the Miro API at once.

In this case, I was using Axios in a Node application to send requests for multiple items’ tag information via the map() API. However, since I was processing hundreds of items concurrently in asynchronous operations, it appears that the Miro API was overwhelmed by the volume of requests, resulting in the 500 errors.

According to Miro’s rate-limiting documentation, exceeding the rate limit should typically return a 429 status code. However, in this situation, there was no rate limit credit exhaustion. I suspect the error was simply due to the excessive load within a very short timeframe.

koalageddon
Forum|alt.badge.img
  • koalageddon
  • New Here
  • 1 reply
  • January 24, 2025

A 500 error on the "get-tags-from-item" endpoint usually indicates an issue with the server or the request handling. I have faced this before  and checking server logs and ensuring the endpoint is receiving the correct parameters often helps resolve it. Anyone else come across this error and found a solution?


Terms & ConditionsAccessibility statement