EventcubeDevelopers

Embeds

Embed a ticket box office on your website

The fastest route to selling. One snippet renders your store inside your own site, resizes itself to fit, and carries your branding all the way through checkout.

Talk to usWhere to find your code

Quickstart

Copy one snippet

Every event has a ready-made embed code in the Eventcube admin, under the event overview page next to the social sharing links. Paste it wherever the box office should appear.

It sizes itself

The snippet loads iframeSizer and calls iFrameResize(), so the iframe grows and shrinks with its contents instead of leaving you a fixed-height box with a scrollbar.

It stays on your brand

The store renders in embed mode via ?embed=true, which drops the surrounding store chrome and inherits the styling you have configured.

No backend work

Payment, ticket delivery, confirmation emails and check-in all continue to run on Eventcube. There is nothing to host and nothing to maintain.

Embed snippet
<script src="https://d20c5uea2cqk8c.cloudfront.net/_shared/iframeSizer.min.js"></script>
<div id="ecEmbed_123"></div>
<script>
  var eci = document.createElement("iframe");
  document.getElementById("ecEmbed_123").appendChild(eci);
  eci.src = "https://your-store.eventcube.io/e/your-event?embed=true";
  eci.setAttribute("id", "ecEmbedIframe_123");
  eci.setAttribute("frameborder", "0");
  eci.setAttribute("style", "width:1px;min-width:100%;height:1000px;min-height:200px;border:none;");
  setTimeout(function () {
    iFrameResize({ checkOrigin: false }, "#ecEmbedIframe_123");
  }, 500);
</script>

EC Pro

Enhanced embeds

Three query parameters turn a standalone box office into part of your product. Each one is a URL-encoded value appended to the iframe src.

prefill

Pass what you already know about the buyer so they don’t retype it. A URL-encoded JSON object, mapped onto the checkout’s billing fields.

Supported fields

nameemailaddress_1address_2citycountrypostcodephone

Anything outside this list is ignored rather than rejected.

prefill
{
  "name": "Jane Smith",
  "email": "j.smith@example.com",
  "city": "London",
  "country": "GB"
}
// then, URL-encoded onto the embed src:
?embed=true&prefill=%7B%22name%22%3A%22Jane...

checkout_data

Your own identifiers, carried through the purchase and attached to the resulting order. Typically the user ID in your system, so you can reconcile a sale back to an account.

You read it back as custom_data on the order:

GET /api/v1/orders/{reference} →

checkout_data → custom_data
// sent in
{ "userId": "abc123" }
// GET /api/v1/orders/EC-1234
{
  "reference": "EC-1234",
  "status": "paid",
  "custom_data": { "userId": "abc123" }
}

success_redirect_url

Send the buyer back into your own flow once payment succeeds, instead of leaving them on the Eventcube confirmation page.

Eventcube appends ec_reference to the URL you supply, so the landing page knows which order it is looking at without a lookup round-trip.

success_redirect_url
# you pass
https://www.example.com/success
# buyer lands on
https://www.example.com/success?ec_reference=EC-1234

Enhanced embeds are an EC Pro feature. See what else is on EC Pro.

Outgrown it?

When an embed stops being enough

If you need your own cart UI, your own event listing, or to create events from another system, the Storefront API covers all of it — and nothing you built with embeds is wasted, because both run against the same store.

Look at the API

Not sure which embed you need?

Send us the page you want to sell from and we'll tell you whether a quickstart embed does the job or whether it's worth going further.

Talk to usRead the docs