Send Customers into Their Portal

1. Publish the stable portal URL

Every organization has:

https://getruba.com/<organization-slug>/portal

The customer enters the email used for purchase and completes the one-time code sent by Ruba. This permanent URL fits a help menu, support article, or marketing site.

2. Hand off an authenticated customer

When the customer is already signed into your product, create a short-lived customer session on your server and redirect to its customer_portal_url.

TypeScript

import { Ruba } from "@getruba/sdk";

const ruba = new Ruba({ accessToken: process.env.RUBA_ACCESS_TOKEN ?? "" });
const { data, error } = await ruba.POST("/v1/customer-sessions/", {
  body: { customer_id: "<customer_id>" },
});

if (error) throw new Error("Unable to create customer session");
redirect(data.customer_portal_url);

Generate this URL at click time. Do not store it as a permanent link because the session token expires.

3. Use links already present in email

Ruba includes a portal route in order confirmations, renewal and subscription-update messages, and failed-payment notices. Those messages preserve a recovery path even when your product does not link to the portal directly.

Launch Path

Shape the Offer

Run the Revenue Model

Deliver Customer Access

Build the Integration

Operate the Business

Implementation Playbooks

Send Customers into Their Portal

1. Publish the stable portal URL

2. Hand off an authenticated customer

3. Use links already present in email

​1. Publish the stable portal URL

​2. Hand off an authenticated customer

​3. Use links already present in email

1. Publish the stable portal URL

2. Hand off an authenticated customer

3. Use links already present in email