Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Interact with Pakat email marketing API (new.pakat.net) - REQUIRES PAKAT_API_KEY environment variable. Use when the user wants to manage email lists, subscri...
Interact with Pakat email marketing API (new.pakat.net) - REQUIRES PAKAT_API_KEY environment variable. Use when the user wants to manage email lists, subscri...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Pakat is a Persian/Farsi-friendly email marketing platform for creating and managing mailing lists, sending campaigns, transactional emails, and tracking delivery โ all via a clean REST API. ๐ Sign up for Pakat to get started.
Require env var PAKAT_API_KEY. If not set, ask the user for their API key. Get your API key from: https://new.pakat.net/customer/api-keys/index export PAKAT_API_KEY="your-key-here"
Base URL: https://new.pakat.net/api # GET requests curl -s -H "X-API-KEY: $PAKAT_API_KEY" "https://new.pakat.net/api/{endpoint}" # POST requests (multipart/form-data) curl -s -X POST -H "X-API-KEY: $PAKAT_API_KEY" \ -F "field=value" \ "https://new.pakat.net/api/{endpoint}" # PUT requests (x-www-form-urlencoded) curl -s -X PUT -H "X-API-KEY: $PAKAT_API_KEY" \ -d "field=value" \ "https://new.pakat.net/api/{endpoint}" # DELETE requests curl -s -X DELETE -H "X-API-KEY: $PAKAT_API_KEY" "https://new.pakat.net/api/{endpoint}"
curl -s -H "X-API-KEY: $PAKAT_API_KEY" "https://new.pakat.net/api/lists"
curl -s -X POST -H "X-API-KEY: $PAKAT_API_KEY" \ -F "EMAIL=user@example.com" \ -F "FNAME=John" \ -F "LNAME=Doe" \ "https://new.pakat.net/api/lists/{list_uid}/subscribers"
curl -s -X POST -H "X-API-KEY: $PAKAT_API_KEY" \ -F "campaign[name]=My Campaign" \ -F "campaign[from_name]=Sender Name" \ -F "campaign[from_email]=sender@domain.com" \ -F "campaign[subject]=Email Subject" \ -F "campaign[reply_to]=reply@domain.com" \ -F "campaign[send_at]=2025-01-15 10:00:00" \ -F "campaign[list_uid]=LIST_UID_HERE" \ -F "campaign[template][template_uid]=TEMPLATE_UID" \ "https://new.pakat.net/api/campaigns"
# Encode HTML content safely using a heredoc BODY_B64=$(base64 -w0 <<'EOF' <h1>Hello</h1><p>Your order is confirmed.</p> EOF ) curl -s -X POST -H "X-API-KEY: $PAKAT_API_KEY" \ -F "email[to_name]=John Doe" \ -F "email[to_email]=john@example.com" \ -F "email[from_name]=My App" \ -F "email[subject]=Order Confirmation" \ -F "email[body]=$BODY_B64" \ -F "email[send_at]=2025-01-15 10:00:00" \ "https://new.pakat.net/api/transactional-emails"
curl -s -H "X-API-KEY: $PAKAT_API_KEY" "https://new.pakat.net/api/campaigns/{campaign_uid}/stats"
HTML content must be base64-encoded (campaign[template][content], email[body], template[content]) Safe encoding: When encoding user-provided HTML content, use heredocs (base64 <<'EOF') or write to a temporary file first to avoid shell injection vulnerabilities. Never use echo with unsanitized input. Transactional email send_at is UTC, format: Y-m-d H:i:s Campaign send_at uses the customer's configured timezone Transactional templates: Set email[template_uid] to use a template instead of email[body]. Use email[params][key] for {{ params.key }} placeholders Subscriber statuses: unconfirmed, confirmed, blacklisted, unsubscribed, unapproved, disabled, moved Pagination: Use ?page=N&per_page=N query params on list endpoints from_email for transactional emails must be on a verified domain
For complete endpoint details, request/response schemas, and all available fields, read references/api_reference.md. For the raw OpenAPI 3.0 spec, see references/openapi.json.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.