Hello. If I use the JavaScript SDK to

Hello. If I use the JavaScript SDK to call the V2 API using the method, importMetadataTML() with the TML below then it responds with a 403 which I'm pretty sure is masking a 500. Anyway, we don't really have confidence in the API if it sometimes returns a 403 and we are relying on it to handle deployments. I'm pretty sure it's something to do with the HTML
{"guid": "4f6ee881-a94a-409b-8254-0f2a5c93465d","liveboard": {"name": "ImporTest","visualizations": [{"id": "Viz_1","viz_guid": "5fa44a49-9900-46c6-9eee-2f378c4212bc","note_tile": {"html_parsed_string": "<h1 dir=\"ltr\"><span style=\"white-space: pre-wrap;\">Test</span></h1><p class=\"theme-module__editor-paragraph\" dir=\"ltr\"><span style=\"white-space: pre-wrap;\">This is a test liveboard for the deployment process</span></p><div class=\"pinboard-note-tile-module__noteTileBg editor-module__bgNode\" style=\"background-color: rgb(255, 255, 255);\"></div>"}}],"layout": {"tiles": [{"visualization_id": "Viz_1","x": 0,"y": 0,"height": 4,"width": 3}]}}}
{"guid": "4f6ee881-a94a-409b-8254-0f2a5c93465d","liveboard": {"name": "ImporTest","visualizations": [{"id": "Viz_1","viz_guid": "5fa44a49-9900-46c6-9eee-2f378c4212bc","note_tile": {"html_parsed_string": "<h1 dir=\"ltr\"><span style=\"white-space: pre-wrap;\">Test</span></h1><p class=\"theme-module__editor-paragraph\" dir=\"ltr\"><span style=\"white-space: pre-wrap;\">This is a test liveboard for the deployment process</span></p><div class=\"pinboard-note-tile-module__noteTileBg editor-module__bgNode\" style=\"background-color: rgb(255, 255, 255);\"></div>"}}],"layout": {"tiles": [{"visualization_id": "Viz_1","x": 0,"y": 0,"height": 4,"width": 3}]}}}
12 Replies
shikharTS
shikharTS6mo ago
Can we get the full API response to understand why 403 is coming?
Benedict
BenedictOP6mo ago
Error: HTTP-Code: 403
Message: Forbidden access.
Body: {}
Headers: {"connection":"keep-alive","content-length":"118","content-type":"text/html","date":"Thu, 05 Sep 2024 12:47:05 GMT","server":"awselb/2.0"}
Error: HTTP-Code: 403
Message: Forbidden access.
Body: {}
Headers: {"connection":"keep-alive","content-length":"118","content-type":"text/html","date":"Thu, 05 Sep 2024 12:47:05 GMT","server":"awselb/2.0"}
There's not a lot to go on. I'm afraid, you'll prob need to debug it
shikharTS
shikharTS6mo ago
Can I have the cluster name? Also are other APIs working? Is the problem only with this one API?
utsav.kapoor
utsav.kapoor6mo ago
@Benedict - Can you also share the response headers with us ?
shikharTS
shikharTS6mo ago
I think I can repro it @Benedict @utsav.kapoor . Let me check if we do allow HTML tags as part of payload. That might be the issue..
Benedict
BenedictOP6mo ago
@utsav.kapoor the response headers are there
utsav.kapoor
utsav.kapoor6mo ago
This is a true 403. The error response is getting triggered by AWS ALB as the request will have a triggered a WAF rule violation. We have asked our cloud team to take a look and unblock
Benedict
BenedictOP5mo ago
thank you Have you any update on this?
shikharTS
shikharTS5mo ago
Hi @Benedict we have found the solution for this. We are testing it out. I will update here once the fix for this is out.
Benedict
BenedictOP5mo ago
Do you have an update?
shikharTS
shikharTS5mo ago
Hi, sorry for the missed update @Benedict , the team is in the process of deploying the fix, I will update here. We should be surely done by end of week. Also have you created a support ticket for this? I would recommend pushing there as it will be through official TS support system.

Did you find this page helpful?