Coaster Credit Logbook

Any ACE web property, kiosk, or partner park app logs a credit by calling one authenticated endpoint. You stay in control of when and where a credit is recorded.

Log a credit via the API

That button really posts to the endpoint below with this member's signed token and updates the log in place.

POST /api/credits
Content-Type: application/json

{
  "memberId":  "M20001",
  "coasterId": "steelvengeance",
  "token":     "8002b41ac37ad317ce58c8d1"
}

200 OK
{ "ok": true,
  "credit": { "name": "Steel Vengeance", "park": "Cedar Point", "source": "api" },
  "totalCredits": 91 }

<script src="https://acebeta.luciapps.com/ace-credits.js"></script>
<script>
  ACECredits.init({ memberId: "M20001", token: "8002b41ac37ad317ce58c8d1" });
  // e.g. from a ride-photo kiosk or a park check-in button:
  ACECredits.log("steelvengeance")
    .then(function (r) { console.log("credit #" + r.totalCredits); });
</script>

The token is minted per member on ACE's server and handed to trusted surfaces only; it never exposes the signing secret.

The deeper integration: Thoosie's on-ride detection recognises when the member actually rides and pushes the credit straight into ACE. No endpoint to call, no button to tap, no member action at all.

Simulate a ride detected by Thoosie

Simulates Thoosie's server recognising an on-ride event and auto-capturing the credit. Watch the log and total update with a Thoosie tag — no tap required.

• Zero member effort. Credits appear because the ride happened, not because someone remembered to log it.
• Higher fidelity. Detection is tied to the actual ride cycle, so counts reflect reality.
• Server to server. Thoosie authenticates to ACE directly; nothing depends on the member's phone being out.

In production this is a signed server-to-server webhook from Thoosie. The button here stands in for that push so you can see the result immediately.