Skip to content
LinkProfit

Offering the API to your clients

How a white-label partner documents and resells the API under their own brand: shared host, client-owned keys, plan gating.

Updated August 13, 2026

Your clients can automate their links the same way you automate your partner account. This page is the playbook for turning the API into a feature of your product — including the text you can adapt for your own developer docs.

How it works

  • Clients create their own keys. Every workspace on a plan with API access has Settings → API keys in the branded dashboard. Keys belong to the workspace: your partner key is never involved, and a client can only reach their own data.
  • The host is shared. All requests go to https://api.linkprofit.com/v1. In v1 a custom API domain per partner is not available — document the host as the technical endpoint of your service. Responses carry no LinkProfit branding: domains, links and analytics in the payloads are your client’s own.
  • You control who gets it. API access is the api_access flag on the plans you sell. Clients on plans without the flag get 403 plan_restricted — a clean upsell moment. Rate limits follow the key, so a heavier plan can ship with a higher limit.

What to put in your docs

A minimal developer page for your clients needs four things:

  1. Where keys live — “Settings → API keys in your dashboard; the key is shown once”.
  2. The base URL — https://api.linkprofit.com/v1, authentication with Authorization: Bearer <key>.
  3. A quickstart — copy the Quickstart and replace the example domain with one of yours.
  4. The reference — link to the interactive reference or host the OpenAPI file (https://linkprofit.com/openapi.json) in your own docs tool; it renders in Scalar, Swagger UI, Redoc and Postman as-is.

Webhooks for clients

Client workspaces register their own webhook endpoints for link, domain and click-threshold events. Partner-level events — subscriptions, payments — stay on your partner endpoints and are never delivered to clients.

Limits worth mentioning

  • Keys are per-workspace: an agency client managing several workspaces creates a key in each.
  • The audit trail attributes API changes to the key, visible to the client in their dashboard — support conversations start with facts.
  • Everything the API writes obeys the same plan quotas as the dashboard: a client cannot script their way past the link limit you sold them.