Domo Programmatic Filtering

Control what data each viewer sees in embedded Domo content via server-side filters and dataset switching. Enforced by Domo — end users can't bypass. For client-side filtering, see cap-de-jsapi-filters.

How It Works

A proxy user (service account) acts on behalf of all viewers. Your server:

1. Authenticates with Domo (OAuth client credentials → access token)
2. Requests an embed token with viewer-specific filters
3. Returns the token to the client, which POSTs it to an iframe

Prerequisites

• Domo API client with CLIENT_ID and CLIENT_SECRET (developer.domo.com > My Account > New Client)
• Embed ID (5-char ID from the embed dialog, not the page URL)
• Dataset column names/IDs for filtering

All auth must happen server-side (CORS restrictions). Never expose credentials client-side.