Issues with embed

  • 28 November 2023
  • 3 replies


Just recently, the embed instructions noted here have stopped working:


Using the invocation code:



                url: '',

                parentElement: document.getElementById('calendly-modal-body'),

                prefill: {}



Spawns a request to Calendly that ultimately returns this response


Age: 9545

cf-cache-status: DYNAMIC

cf-ray: 82d4ad0a0b103705-YYZ

Content-Encoding: br

Content-Type: text/html; charset=utf-8

Date: Tue, 28 Nov 2023 18:29:21 GMT

Last-Modified: Tue, 28 Nov 2023 15:50:04 GMT

Server: cloudflare

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

Vary: Accept-Encoding, Origin

Via: 1.1 (CloudFront)

x-amz-cf-id: qnDkzkCQ-DxfUc_z4Pp1jZA24f5UoczK1oqvza1rvhS0u98DWrPW4A==

x-amz-cf-pop: YUL62-C2

x-amz-version-id: EVin17i.0_5u4mmzATuQGsDtuQywgDL1

x-cache: Hit from cloudfront

X-Content-Type-Options: nosniff

X-Frame-Options: DENY



The X-Frame-Options: DENY is the kicker, since the Calendly.initInlineWidget call spawns within an iFrame.


In other words, the javascript says: load _this_ in an iFrame

The iframe body request says: no iFrames allowed.


New bug?


Best answer by marion-calendly 28 November 2023, 21:55

View original

This topic has been closed for comments

3 replies

Userlevel 2

Hi @LemonadeLXP !

We experienced an incident earlier that affected routing forms (see our Status page) which would have resulted in the embed code loading a page that could not be displayed in an iframe. Based on the timing of your post, I think you may have been impacted by this.

If you’re still seeing the same result, I would also recommend checking that the link you have passed to the code is valid (e.g. by loading it in your browser directly). Our 404 page also has X-Frame-Options: DENY so this is the most common reason for seeing that in our embed.

Thank you for confirming.

Userlevel 7

Thank you for confirming.

We are so glad this helped! Let us know if you have further issues. Have a great day!