Getting Your Product Key & Secret
Every Product has two credentials. You pass both to Sdk::bootstrap() (see
Initializing the SDK).
Product Key (pk_...) | Product Secret (sk_...) | |
|---|---|---|
| What it does | Identifies which Product data belongs to | Used to cryptographically sign requests, proving they’re genuine |
| Sensitivity | Low risk if seen | High risk if leaked — treat like a password |
| Where to find it again | Product settings in the Org Panel (always visible) | Shown once, at creation — copy it immediately |
Where to find them
- Go to Organization Panel → Products → [Your Product] → API Keys.
- The Product Key (
pk_...) is always visible and copyable. - The Product Secret (
sk_...) is shown only once, right after the Product is created (or after you regenerate it). Copy it somewhere safe immediately — Appneck cannot show it to you again.
Lost your secret? Regenerate it from the same screen. Regenerating immediately invalidates the old secret — any plugin still using the old one will start failing requests, so only regenerate if you’ve genuinely lost it or believe it’s exposed.
How they’re used in code
Both are passed to bootstrap() — the key and secret are the first two
arguments:
\Appneck\Sdk\Sdk::bootstrap(
'pk_your_product_key', // Product Key
'sk_your_product_secret', // Product Secret
'https://appneck.com',
__FILE__
);The SDK does the signing math for you — you never implement any of the cryptography yourself.
Keeping the secret safe
- Never commit it to a public repository.
- If your plugin’s source is publicly distributed (e.g. WordPress.org), don’t hardcode the secret directly in a committed file. Load it from a file excluded from your public repo, or fetch it at runtime, so it isn’t readable in your public source.
Next: Installing the SDK →