Skip to main content
The Embeddables Secure Proxy is great for solving one or both of the following when calling APIs from the frontend in an Embeddable:
  • You want to call an API that requires a credential, but you don’t want to that credential to be exposed on the frontend.
  • You’re having issues with CORS when calling an API from the frontend.

​
How the Secure Proxy Works

The new proxy comes with the following features:
  • Allowlisting of endpoints and credentials: Only allowlisted endpoints and credentials can be used for the specific environment + project combination. Disallowlisted endpoints or credentials will be blocked.
  • Request results are returned as-is: The proxy does not tamper with the received requests in any way. What you see is what you get.
  • X-Proxy-Worker-Success header: This header will be true if the proxy made your request, and false if it wasn’t able to for some reason. If you receive a 400 response and are unsure if it’s coming from the proxy or the final destination, check this header.

​
Adding Credentials and Endpoints in Project Settings

1

Go to Project Settings

Navigate to your project’s settings and select the Credentials & Endpoints tab.
2

Add Credentials

Click the + New Credential button and fill in the required fields:
  • Service Type: Select the type of service (e.g., EHR, CRM, etc.)
  • Service Name: The name of the service (e.g., Tellescope, CareGLP, etc.)
  • Key Type: The type of key (e.g., API Key, Token, etc.)
  • Environment: Choose the environment (Production, Staging, etc.)
  • Label: A descriptive label for your credential
  • Value: The actual credential value (the secret that you’re protecting)
Your credentials will appear in the list, each with a unique identifier and label.
3

Add Endpoints

Click the + New Endpoint button and fill in the required fields:
  • Label: A descriptive label for the endpoint
  • Environment: Select the environment
  • Allowed Origins (Regex): Regex for allowlisted origins (e.g., your frontend domains)
  • Allowed Destinations (Regex): Regex for allowlisted API destinations
  • Credential IDs: Select the credentials that can be used with this endpoint
Your endpoints will appear in the list, showing the allowlisted origins, destinations, and associated credentials.

​
Using Credentials in Your API Requests

Once your credentials and endpoints are set up, you can use them in your API calls through the proxy. Here’s an example of how to use a credential in your request headers: 
const weightLossProductsOptions = {
  method: "POST",
  headers: {
    "My-Secret-Header": "{{cred_aaaaaaaaaaaaaa}}", // Use the credential reference here
    "Content-Type": "application/json",
    "X-Environment": "prod",
    "X-Project-ID": "pr_bbbbbbbbbbbbbb",
  },
  body: JSON.stringify(weightLossProductsBody),
};

fetch(
  `https://proxy-worker.heysavvy.workers.dev/?url=${encodeURIComponent(
    "https://api.example.com/api/v1/endpoint"
  )}`,
  weightLossProductsOptions
)
  .then((response) => {
    // handle response
  })
  .catch((err) => console.error(err));
  • Replace the following placeholders with your actual values:
    • My-Secret-Header —> the header name that you want to use to pass the credential value.
    • {{cred_aaaaaaaaaaaaaa}} —> the credential ID that you created previously. You might alternatively want to use a credential in the URL or body instead of a header. Either way, the proxy will inject the actual credential value for you.
    • prod —> the environment you want to call the endpoint in.
    • pr_bbbbbbbbbbbbbb —> the project ID for your project (grab it from the URL in the Embeddables Web App - it’s the ID after /project/).
    • https://api.example.com/api/v1/endpoint —> the actual endpoint you want to call.
  • Make sure the endpoint and credential are both allowlisted with the project and environment that you’re using.
⌘I