Functional cookies only

Lyrinox Market uses functional cookies for login sessions, security, preferences, and faster account lookups. You can disable persistent functional cookies in account settings.

Privacy

docs

How API Keys Work on Lyrinox Market

What API access is for, why it is reviewed, and how approved users should think about protecting their keys.

How API Keys Work on Lyrinox Market

API keys are for people building real integrations.

They are powerful enough that Lyrinox Market does not treat them as a casual account setting. API access is reviewed so we can protect buyers, sellers, product data, licensing systems, and marketplace operations.

Why API access is reviewed

An API can touch parts of the marketplace that normal browsing cannot.

Depending on the feature, an integration may interact with:

  • Product data.
  • Licenses.
  • Downloads.
  • Orders.
  • Seller tools.
  • Account-level automation.

That access should go to users with a clear reason to use it.

What API keys are useful for

Approved API access may be useful for:

  • License validation.
  • Product delivery workflows.
  • Seller operations.
  • Internal business tools.
  • Reporting.
  • Support automation.
  • Marketplace integrations.

If you only need to buy, download, or manage products manually, you probably do not need an API key.

Protect API keys like passwords

API keys should never be shared publicly, committed to source control, pasted into screenshots, or shipped inside client-side code.

If a key is exposed, revoke it from your settings and create a replacement.

Applying for access

API access can be requested from account settings. A real person reviews the request before API keys can be used.

This helps keep the platform useful without turning API access into an open door.

For security concerns, contact [[email protected]](mailto:[email protected]). For account help, contact [[email protected]](mailto:[email protected]).