fupisha.NYARAKA
/
Dashibodi
Documentation Getting started

Unganisha Fupisha kwenye mtiririko wako wa kazi.

Unda viungo vifupi vyenye chapa, fuatilia kampeni zako, na unganisha mfumo wako kwa API moja safi.

Start with a test key. Test keys use the same API contract without affecting your production workspace.

Create your first link

Send a destination URL to the Links API. Use your API key as a bearer token.

POSThttps://api.fupisha.link/v1/links
curl -X POST https://api.fupisha.link/v1/links \
  -H "Authorization: Bearer $FUPISHA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com/campaign"}'

Response

{
  "id": "lnk_7q...",
  "short_url": "https://fupisha.link/aB3xK9",
  "destination_url": "https://example.com/campaign",
  "redirect_type": 302,
  "status": "active"
}

Authentication

Keys belong to a workspace and can be limited to scopes such as links:write, links:read and bulk:write. Keep production keys on your server; never put them in client-side code.

Bulk campaign links

Create a recipient-specific link per row. Send an Idempotency-Key so retries return the original operation result. Bulk creation is bounded and returns row-level errors.

Custom domains

Verify ownership with the displayed DNS records before using a branded hostname. HTTPS certificates are provisioned only for verified domains.

Webhooks

Fupisha signs event payloads. Verify the signature and deduplicate deliveries using their event ID.

MCP server

{
  "mcpServers": {
    "fupisha": {
      "url": "https://mcp.fupisha.link",
      "headers": { "Authorization": "Bearer fpk_live_..." }
    }
  }
}

SDKs

TypeScriptGoPythonPHP
UP NEXTAuthentication & API keys
This documentation is under active development. Contact us.