Build with Fendsy

Connect your customer experience.

Use your server for trusted customer and order facts. Use your Site ID and Web SDK for browser activity. Fendsy keeps those sources distinct so a page view cannot become a verified purchase.

Verify your keyCopy-tested cURL, Node and Python examples for your first API call.Reuse privacy setupCopy Site details and consent pages within a workspace, then review and publish.Connect a SiteInstall Fendsy on a Shopify theme, headless storefront, or ordinary website.Confirm an orderSubmit a merchant order, record milestones, and recover safely from retries.Request a ReviewUse an order-bound Journey action and keep verified purchase claims accurate.Report SaaS factsConnect account, workspace, trial and plan outcomes to a Customer Profile.Build an audienceCreate a Customer Profile, maintain static Lists, and activate Segment drafts.Send a templateQueue one eligible marketing or merchant order service email and follow its status.Run a CampaignPrepare a draft, validate its audience and sender, then follow the run.Read resultsCheck event receipts, saved reports, Customer orders, and account billing.Browse the APISee only the operations callable with a server credential and their required scopes.

Start with a server key

  1. Open Settings → Developer in your Fendsy workspace.
  2. Create a key with only the scopes your integration needs. Copy it once into your server secret manager.
  3. Verify the key and workspace ID before sending data.
curl https://api.fendsy.com/v1/credentials/verify \
  -H "Authorization: Bearer $FENDSY_API_KEY"

Never put a server key in browser code. A key cannot act as a signed-in workspace owner.

Send a server event

Grant the key events:write and bind it to the intended Site. Every event needs an idempotency key and an explicit customer subject. An accepted receipt means Fendsy received the event; it does not prove downstream processing or Journey eligibility.

A custom event can be inspected before activation. Review its schema, consent and allowed uses before a Journey or Segment can consume it.