Now your custom landing pages can call your own APIs, and BigMarker makes each call for them. With the Landing Page Connector, your API key is kept on BigMarker, never in the page, and visitors only get the fields you choose. Set it up per webinar, under Integrations.
Seats left at each location, a member lookup, a list your team keeps current: a custom landing page can now ask your own API for it. The page calls BigMarker, BigMarker calls your API with the headers you saved, and the page gets back only the fields you listed. You never put a key in the page.

Open your webinar, then Integrations › Landing Page Connector.


{{ inputs.name }}. Anything else the page sends is dropped.


Anyone who has the page's address can then call the action, including from a script, so list only fields that are fine to show to anyone. For an action that sends data to your API, the card shows a stronger warning.
Each action card has a How your page calls it panel with two things to copy. Add the token to the page's HTML once, then call the action by its key. Every action is called the same way; the page never picks the address, the method or the headers.

In the video, a visitor types a state and clicks Search, and the three locations come from the company's own API.

The call always resolves. res.success says whether it went through, and res.data holds only the fields you listed. When it didn't, res.error says why.
| res.error | What happened |
|---|---|
invalid_input | A required input is missing, or an input isn't valid. res.field names the input, and your API isn't called |
registration_required | The action is for registered visitors, and this visitor isn't one |
not_found | No action has that key, or the action is off |
rate_limited | Too many calls in a minute, or your API answered 429 |
unavailable | Your API couldn't be reached, answered with another non-2xx status or a redirect, took longer than 5 seconds, or sent more than 1 MB |
expired | The page has been open too long: reload it |
busy | An identical call was already on its way and didn't finish in about ten seconds |
network | The browser couldn't reach BigMarker |
| Details | |
|---|---|
| Your API | An HTTPS address on the public internet. BigMarker checks it when you save and again on every call. Responses are read as JSON |
| Several APIs | Add a connection for each API. Each one gets its own tab, headers and actions |
| Methods | GET, POST, PUT, PATCH or DELETE. For every method except GET, a Request body (JSON) field appears. A test of one of those really sends it to your API |
| Registered visitors | The path and body can also use registrant.email, registrant.first_name, registrant.last_name and registrant.registration_id |
| Cache results | For a GET, or a POST that only reads: visitors making the same call with the same inputs get the response BigMarker already has, for as long as you set (120 seconds to start, up to 3600). Not for actions that use a registrant token |
| Call Log | The Call Log tab lists your test calls and the page calls that failed at your API, with the connection and action |
| Copies | Copying the webinar copies its connections and actions. A copy into another channel leaves the secret values behind and starts with its actions off |
