Skip to main content
Most applications use two SDKs:
  1. A client SDK creates a stable visitorId.
  2. The Node SDK sends the conversation to Era and returns a context block.

SDK comparison

Never put a Node SDK API key in browser or mobile code.

Browser application

Use the Web SDK in the browser and the Node SDK on your backend.
Browser
Trusted backend

Flutter application

Use era_flutter in the app and the Node SDK on your backend.
Flutter
Send visitorId with the chat request. Your backend uses it in the same turnContext() call shown above.

Backend-only application

The Node SDK still needs a stable visitorId. Create and store one for each user or visitor, then pass it on every turn.

Signed-in users

When your backend knows the signed-in user, add your own stable user ID:
partnerEndUserId adds trusted account identity, but it does not replace visitorId. Only send email or phone assertions that your backend has already verified.

Node SDK quickstart

Request your first context block.

Web SDK quickstart

Create a browser visitor.

Flutter SDK quickstart

Create a mobile visitor.