What does the RevenueDot webhook event TEMPORARY_ENTITLEMENT_GRANT mean?
The RevenueDot webhook event TEMPORARY_ENTITLEMENT_GRANT is never sent, because RevenueDot never grants access that the store has not verified.
Quick facts#
| Event | TEMPORARY_ENTITLEMENT_GRANT |
| Where | RevenueDot webhook (event.type), RevenueCat's webhook format |
| Sent to | No webhook: it is never sent |
| Fields that are specific to it | none |
| What it means | A RevenueCat event type for access granted without a verified purchase, during a store outage. RevenueDot accepts it in a webhook's event_types filter and never sends it. |
When it is sent#
- RevenueCat sends it when it grants a temporary entitlement while a store is down.
- RevenueDot never has that fact: it does not grant access it has not verified with the store.
- During a store outage the SDK keeps the purchase and grants access on the device from the offline entitlement mapping.
What your server should do#
- Do not wait for this event. Your handler may keep a case for it so a RevenueCat handler still compiles.
- If you migrate from RevenueCat, remove any logic that depends on it, or keep it as a no-op.
- Use the offline entitlements guide for how access works during an outage.
- Deduplicate on
event.id: deliveries can repeat, because anything but HTTP 200 is retried after 5, 10, 20, 40 and 80 minutes.
Example#
JavaScript
import { createHmac, timingSafeEqual } from "node:crypto";
// X-RevenueCat-Webhook-Signature: t=<unix seconds>,v1=<hex HMAC-SHA256 of "<t>.<raw body>">
function verify(rawBody, header, secret, toleranceSeconds = 300) {
const m = /^t=(\d+),v1=([0-9a-f]{64})$/.exec(header ?? "");
if (!m || Math.abs(Date.now() / 1000 - Number(m[1])) > toleranceSeconds) return false;
const expected = createHmac("sha256", secret).update(`${m[1]}.${rawBody}`).digest();
return timingSafeEqual(expected, Buffer.from(m[2], "hex"));
}
// Sign a sample delivery the way RevenueDot does, then handle it.
const secret = "whsec_test_secret";
const rawBody = JSON.stringify({ api_version: "1.0", event: {"id":"66339910-3BFF-49F4-B873-D1283D673DE2","type":"TEMPORARY_ENTITLEMENT_GRANT","app_user_id":"user_1","product_id":"pro_monthly"} });
const t = Math.floor(Date.now() / 1000);
const header = `t=${t},v1=${createHmac("sha256", secret).update(`${t}.${rawBody}`).digest("hex")}`;
const seen = new Set(); // use a database table in production
function handle(rawBody, header) {
if (!verify(rawBody, header, secret)) return "401 bad signature";
const { event } = JSON.parse(rawBody);
if (seen.has(event.id)) return "200 duplicate";
seen.add(event.id);
if (event.type !== "TEMPORARY_ENTITLEMENT_GRANT") return "200 ignored";
return "no-op, RevenueDot never sends this";
}
console.log(handle(rawBody, header));Run-checked: npm run check:snippets runs this snippet with Node and compares its output with no-op (checked 2026-10-03).
How RevenueDot produces it#
The type is in EVENT_TYPES so a filter that names it is valid, and in NEVER_SENT_EVENT_TYPES so nothing produces it. That makes 19 of RevenueCat's 21 event types sent.
Related#
- What does the RevenueDot webhook event INVOICE_ISSUANCE mean?
- What does the RevenueDot webhook event INITIAL_PURCHASE mean?
- What does the RevenueDot webhook event TEST mean?
- Which webhook events RevenueDot sends, and the two it never sends
- Webhooks guide: set up, verify and test
Source#
- RevenueDot docs: which webhook events RevenueDot sends
- RevenueCat: webhook event types and fields (the format RevenueDot follows)
- RevenueDot core: events.ts (the event types and the rules that derive them)
Checked: 2026-10-03