Node SDK proxy

This is the client path for the Node SDK. Routing the SDK through the proxy lets you keep the OAuth keys out of the SDK client entirely: the SDK sends its requests to the proxy, and the proxy holds the public and private keys and attaches the credentials on the way to Mambo.

Point the SDK at the proxy

Set the SDK's baseUrl to your proxy and use the NoAuthAuthenticator, so the client carries no credentials of its own.

Node.js

import { MamboClient, NoAuthAuthenticator } from '@mambo/sdk';

// No credentials in the client — the proxy adds them.
const client = new MamboClient({
  baseUrl: 'https://app.acmeinc.com/mambo', // your proxy, not https://api.mambo.io
  authenticator: new NoAuthAuthenticator()
});

await client.activities.createAsync({ siteUrl: 'acmeinc' }, data);

What the proxy does for this path

• Holds the OAuth keys. The public and private keys live only in the proxy. It exchanges them for a bearer token and attaches it to each forwarded request, so the token never reaches the SDK client.
• Forwards to the Mambo REST API. Requests the SDK would have sent to https://api.mambo.io are sent to your proxy instead and relayed on.

Note

The proxy authenticates to Mambo, not your end users. Your own application is still responsible for authenticating the caller and deciding what they are allowed to do before it makes SDK calls on their behalf.

See the reference implementations for how to run a proxy that serves this path (and the widget path) and how to supply the keys it needs.