Skip to main content

What's New

Notable changes to the relay Embedded SDK. Additive changes are backwards-compatible — existing integrations continue to work without modification.

v0.16.0 — Takeover handlers for print and download, for native WebViews​

Additive and optional — existing integrations are unaffected.

mount() accepts two new optional handlers, handlePrintRequested and handleDownloadRequested. The embedded view normally prints via window.print() and downloads files via anchor clicks — both browser-native APIs that fail or do nothing inside a native mobile WebView (iOS WKWebView, Android WebView). Providing either handler suppresses that default and delegates the action to your code instead, so a native host can bridge it to a real platform print/download API. Unlike the on* callbacks, these are named handle* because providing one changes the form's behavior rather than just notifying you of something already done. See the new WebView Integration guide and Takeover Handlers in SDK Methods.

v0.14.0 — Additional report bundles for productId​

Additive and optional — existing integrations are unaffected.

screening.productId now accepts 7 additional consumer-platform report bundles (9, 34, 36, 38, 51, 52, 68), alongside the original 4 TSP passive-Identity bundles (71–74). Which bundles are meaningful for your account depends on your Experian product entitlements. See productId in SDK Methods for the full list and what each value includes.

v0.13.0 — Skip the END_USER category selection screen​

Additive and optional — existing integrations are unaffected.

mount()'s screening options accept a new optional endUserType field. The END_USER screening flow normally opens by asking the operator which category they screen under (independent owner, real estate agent, or property management company); when your platform already knows this, supplying endUserType skips that selection screen and starts the wizard directly at the first data-entry step. See endUserType in SDK Methods for accepted values and validation behavior.

v0.12.0 — Session tokens for server-side mount provenance​

Additive and optional — existing integrations are unaffected.

Intellirent.init() accepts two new optional config options: sessionToken, a single-use grant your backend mints via POST /v1/sessions and your frontend presents once at mount, and onTokenExpired, a callback that supplies a replacement if the grant expired before mount completed (the SDK retries the exchange once). Neither is required today — omitting both leaves behavior exactly as before. See the new Session Tokens guide for the full flow, including how to mint a token with a secret key (sk_live_*/sk_test_*).

v0.9.0 — Billing behavior for prepaid accounts​

General availability date is TBD — prepaid credit billing is rolling out to TSPs on a staged basis rather than a fixed public launch date. Partners interested in early access can contact their Intellirent account manager or integration support to discuss eligibility.

Accounts on the prepaid credit billing model now receive a typed balance error when their credit balance is exhausted:

  • Mounting the report view for a specific report delivers an SdkError with code: "PAYMENT_REQUIRED" and recoverable: false to the onError callback when the account balance is $0. The reports list view is not affected — it always renders normally regardless of balance.
  • The embedded view displays a billing-specific message in place of the report.
  • No integration changes are required. Accounts billed per transaction via Stripe Connect are unaffected.

See the Billing guide for the full error contract and recommended handling.