Developer quickstart

Verify your server key.

Create a key in Settings → Developer for the workspace and Site you intend to connect. Store the key only on your server. These examples check its workspace, Site binding, scopes and expiration without sending an event or message.

cURL

Set FENDSY_API_KEY in a Bash server shell, then run this command. In PowerShell, replace $FENDSY_API_KEY with$env:FENDSY_API_KEY.

curl --fail-with-body https://api.fendsy.com/v1/credentials/verify \
  -H "Authorization: Bearer $FENDSY_API_KEY"

Node.js 22+

Save this as verify.mjs and run it with the same environment variable.

const key = process.env.FENDSY_API_KEY
if (!key) throw new Error("Set FENDSY_API_KEY on your server")

const response = await fetch("https://api.fendsy.com/v1/credentials/verify", {
  headers: { Authorization: `Bearer ${key}` },
})
const result = await response.json()
if (!response.ok) throw new Error(`${response.status}: ${JSON.stringify(result)}`)
console.log(JSON.stringify(result, null, 2))

Python 3

Save this as verify.py and run it with the same environment variable.

import json
import os
from urllib.request import Request, urlopen

key = os.environ["FENDSY_API_KEY"]
request = Request("https://api.fendsy.com/v1/credentials/verify", headers={"Authorization": f"Bearer {key}"})
with urlopen(request, timeout=10) as response:
    print(json.dumps(json.load(response), indent=2))

Use the result

The response includes organizationId, optionalsiteId, scopes and expiresAt. A 401 means the key is missing, revoked or expired. Grant only the scopes the next integration needs; a server key cannot act as a signed-in workspace owner.

Next: send a trusted SaaS fact, confirm an order, or browse the API reference.