Skip to content
Contact salesDashboardGet API key
Get startedPaymentsBilling
Documentation navigation

Fynex

API keys

One key authenticates both APIs. There is no second token to obtain for Billing, and no separate Payments credential. If you have a working sk_ key for one, it works for the other.

Where to get one for your own account

  1. Log in to the Fynex dashboard.
  2. Select your seller account.
  3. Open the Integration page and reveal the key on the API keys card.

You issue and rotate it yourself — nobody at Fynex has to do it for you. Keys are stored only as hashes, so a lost key cannot be recovered, only regenerated.

How to send it

Authorization: Bearer sk_test_...

Anything else — a missing header, a malformed value, an unrecognised key — answers 401. This is a server-to-server API: never put a key in a browser, a mobile app, or a query string.

Test or live

The prefix tells you which, and the ACCOUNT decides it, not the host. An account is in demo mode or live mode, never both:

  • sk_test_… — the account is in demo mode. No real money moves.
  • sk_live_… — the account has gone live. Money is real.

After go-live the old test key answers 401. There is no parallel test dataset behind the prefixes: the API always returns your account's own records.

Because mode is decided by the account, an sk_test_ key is test mode wherever you send it.

The older token without a prefix

Accounts created before prefixed keys existed may still hold the original dashboard API token: an opaque string with no sk_ prefix, shown on the same Integration page. It still authenticates the Payments API exactly as before. The Billing API accepts only sk_test_ / sk_live_ keys and answers 401 to it — so if you call both, use the prefixed key for both. Do not parse either shape: treat the whole value as opaque.

Then what