Blog · General

Is the LynxMetrics API secure? Key, account and payments

How LynxMetrics protects API keys, your account and your payments, what you should do on your side so the key does not leak, and what to do if it does.

Published on October 18, 2026 · 4 min read

Before putting an API into your bot or your site, it is normal to ask whether it is secure. The question has two sides: what the provider does to protect your account, your keys and your payment, and what you need to do so the key does not leak. This article covers both, with what LynxMetrics actually does.

What LynxMetrics does on its side

Always-encrypted connections

The site, the dashboard and the API only answer over HTTPS, and the browser is instructed never to try the unencrypted version. Nothing you send or receive, the key included, travels in the clear.

Keys stored encrypted

Every API key is stored in two forms, neither of them plain text. The API checks each request against a hash of the key, which cannot be reversed into the original. So that you can copy the key from the dashboard whenever you want, it is also stored encrypted with AES-256, tied to your account, and it only opens for its owner.

One key per API and per project

Each key opens a single API. The Bac Bo Live key does not reach any other API in the catalogue, and using one API's key on another returns the key_wrong_api error. On top of that, each subscription is a project with up to 5 keys of its own, so you can keep one key per bot, server or client, and rotate one without touching the others.

Masked keys, rotation and revocation

In the dashboard, keys appear masked, with a button to copy when you need it. If a key leaks, the rotate button generates a new one immediately and the old one stops answering within moments.

Limits against abuse

Each plan has a requests-per-minute limit, shared across all the project's keys. If someone takes your key and tries to abuse it, the damage is capped by the limit, and you can see the usage in the dashboard. The sign-in, sign-up and password screens also have per-IP attempt limits, against anyone trying to guess passwords.

Confirmed email

To try an API, the account needs an email confirmed by code. That makes mass fake accounts harder and guarantees that important notices reach you.

Payments happen elsewhere

Card payments happen on Stripe's page, and Pix is generated by Mercado Pago. Your card details never pass through LynxMetrics' servers, which only receive the confirmation that the payment went through.

What you need to do on your side

Most key leaks happen on the API user's side, and almost always for the same reasons.

  • Never put the key in the browser. Page JavaScript is public. If your site needs the data, the browser talks to your server, and only the server calls the API. We show how in a Bac Bo statistics site.
  • Never put the key in your code. Use environment variables, such as LYNX_KEY, or your host's secrets panel.
  • Be careful with GitHub. A public repository with the key in the code is found by bots within minutes. Add the .env file to .gitignore before your first commit.
  • One key per place. If the Telegram bot and the site use different keys, a leak in one does not take down the other.
  • Do not send the key in a screenshot or a group chat. If you need help from support, we never ask for your full key.

My key leaked — now what?

  1. Open the dashboard, go into the project and rotate the leaked key. The old one stops answering within moments.
  2. Update the new key in your bot or server, through the environment variable.
  3. If the key was in a repository, delete the file and remember that it stays in the Git history. That is why step 1 comes first.
  4. Check the project's usage in the dashboard to see whether there were requests that were not yours.

Security is also transparency

A secure API is also an API that does not mislead. LynxMetrics sells data and statistics, not predictions, and publishes the rules for plans, limits and errors in the documentation. If you find a security flaw, talk to us through the email on the contact page.

Frequently asked questions

Does LynxMetrics store my key in plain text?

No. The API checks each request against a hash of the key, and the copy the dashboard shows is encrypted with AES-256, tied to your account.

What happens if my API key leaks?

Rotate the key in the dashboard and the old one stops answering within moments. In the meantime, the plan's per-minute limit caps any misuse, and you can follow the project's usage in the dashboard.

Does LynxMetrics see my card details?

No. Card payments happen on Stripe's page, and Pix is generated by Mercado Pago. LynxMetrics only receives the payment confirmation.

Read also