WLI: Brand creation endpoint — example on a custom backend proxy

🔗Creating a new brand/profile by using the API

This example is shown over a button that activates the call, but it can operate automatically without adding any buttons.

Endpoint overview

The GET - /admin/add-profile endpoint creates a new brand/profile in a Metricool account from your own web app, without your end user ever visiting Metricool directly.

This guide is split into the same parts as the rest of the following White Label Integration (WLI) examples:

1. A button in your frontend that triggers the brand creation.

2. A backend proxy that holds your Metricool API credentials and forwards the request.

Prerequisites

You'll need two values from your Metricool account:

Both are sent on every call: userToken in the X-Mc-Auth request header & userId as a query parameter.

• Unlike the other endpoints, this call does not require a blogId — the brand doesn't exist yet when you make the request, so there's nothing to scope it to.

• Anyway, if you have an automation that adds automatically the blogId, you can use the one associated with the brand already created when registered in your Metricool account.

The following example will continue without adding the blogId, as other sample calls will show that architecture.

— Understand the endpoint —

GET https://app.metricool.com/api/admin/add-profile?userId={userId}

• In Metricool's Swagger spec (tag Admin Service with description "Creates new profile"), this endpoint is listed with no parameters at all.

• The userId requirement comes from the API's general authentication rules, which apply to every call, not from anything specific to this endpoint's own definition.

As mentioned before, blogId query parameter can be included without causing an error, but Metricool ignores it either way.

On success, the endpoint returns 200 with a PublicBlog JS object describing the new brand.

— Call it from the frontend —

Following the example we have discussed during the last two articles, we created a button that collects the confirmation and calls your own backend route — not Metricool directly.

Because userId isn't a secret (it's visible in Metricool's own URL as you browse your account), it's safe to include directly in the request your frontend sends:

<button onclick="crearNuevaMarca()">Create new brand</button>
<script>
async function crearNuevaMarca() {
  if (!confirm('Create a new brand/profile in Metricool?')) return;
  const userId = '${YOUR_METRICOOL_USER_ID}';
  const response = await fetch(`/api/admin/add-profile?userId=${userId}`);
  // Read as text first: error responses aren't guaranteed to be valid JSON.
  const rawText = await response.text();
  let details;
  try { details = JSON.stringify(JSON.parse(rawText), null, 2); }
  catch { details = rawText; }
  alert(response.ok ? `Brand created:\n${details}` : `Error (${response.status}):\n${details}`);
}
</script>

— Security checklist —

• userToken never appears in any file served to the browser.

• Credentials are read from environment variables, not hardcoded.

• The button that triggers this call sits behind a confirmation step and isn't reachable as a plain, crawlable link.

• If a token was ever committed or exposed client-side, regenerate it immediately from Metricool → Account Settings → API.

— Troubleshooting —

Table B

Additional Resources