Already a Spur customer?

Log in
Security

How the embed is protected

Your server proves who’s asking with its API key. Everything after that is short-lived, tied to your site and limited to conversation work.

How it’s protected

Opaque, single-use tokens

A token is a random string, not a JWT. It works once, expires within 60 seconds and leaves the URL as soon as it’s exchanged.

A link alone opens nothing

Each token is bound to a one-time code verifier your page makes (PKCE). Only its hash travels with the mint; the page hands the verifier to the frame with postMessage, and the browser tells Spur which site sent it. An embedUrl that leaks into a log, a screenshot or a proxy can’t be spent.

Short, contained sessions

Sessions last 8 hours and can’t be extended. They live in an HttpOnly, Secure cookie that’s partitioned to your site, so your page’s JavaScript can’t read it and no other site can use it.

Conversation work only

An embed session can open and work on conversations the Spur user is allowed to see. It can’t reach settings, billing, conversation lists or anything else in your workspace, whatever the user’s role.

Framing locked to your origins

The frame only loads inside the origins on your allowed list. That also stops other sites from loading it or tricking people into clicking inside it.

No workspace secrets in the frame

The data Spur sends to the frame leaves out access tokens and payment keys, and is masked for masked users.

Audit trail

Every token is recorded with the API key name, the Spur user, the origin and the time, and kept for 90 days after it expires. Handovers through the assign endpoint show up in the conversation’s history.

What stays on your side

Keep the API key on your server

Never put it in browser code. It can read and send on every conversation in your workspace.

Your CRM login is the gate

Anyone who can sign in to your CRM and open a record can use the frame. Apply your usual access controls there.

Send the verifier to Spur only

Make a new code verifier for every token, keep it in the page, and post it with Spur’s origin as the target, never “*”.

Keep numbers out of the browser

If masking matters, hide the contact’s number in your own CRM too, and keep it out of your browser-side code.

Register your origins

List every site that shows the frame, and remove ones you stop using. Removing a site ends the frames open on it straight away.

Protect the shared user

If your team shares one Spur user, give it a long random password nobody holds, so it can’t be used to sign in to Spur.

Rotating keys

  1. Create a new key in Settings → Developers → API.
  2. Switch your server to it.
  3. Delete the old key. Every embed session minted with it ends at once; open frames post spur:authRequired on their next request, and your page mints with the new key. Your other integrations aren’t touched, as long as the old key was used only for the embed.