Yandex Mail to Webhook

Why Route Yandex Mail Emails to a Webhook?

Yandex Mail is the dominant email service in Russia and widely used across Eastern Europe, Central Asia, and by the Russian diaspora globally. While Yandex Mail is a capable email platform, its native tooling for programmatic automation was not built for developers who need structured, reliable data delivery to backend systems.

The native approach — Yandex Mail IMAP (app password) — introduces significant operational overhead. You need to manage credentials, poll or maintain persistent connections, and write custom parsing logic for every message field you care about. When your team is moving fast, that friction adds up to hours of maintenance per integration.

JsonHook eliminates that overhead by accepting inbound mail on your behalf and immediately firing a structured JSON payload to any HTTPS endpoint you specify. The email is parsed, attachments are base64-encoded, and headers are normalised — so your webhook handler can focus entirely on business logic rather than MIME parsing.

Below are the core benefits of routing your Yandex Mail messages through JsonHook instead of relying on the native alternative:

• Limitation avoided: Yandex Mail's API is limited to the Yandex Connect / 360 business product and is not available for standard consumer Yandex Mail accounts.
• Limitation avoided: IMAP access to Yandex Mail requires enabling it explicitly in settings and using an app password — and Yandex periodically forces password resets that break automated integrations.
• Limitation avoided: Yandex's mail infrastructure can be slow to propagate changes when accessed from outside Russia due to network routing, increasing the latency of polling-based integrations.
• Zero-polling architecture: JsonHook pushes to your endpoint the moment mail arrives — no long-running background jobs needed.
• Automatic attachment handling: PDFs, images, and other file types are extracted, base64-encoded, and included in the JSON payload with their original MIME type.
• Retry with exponential back-off: If your endpoint is temporarily unavailable, JsonHook retries automatically — something the Yandex Mail IMAP (app password) does not do natively.
• Webhook signatures for security: Every delivery includes an HMAC-SHA256 signature header so you can verify the payload originated from JsonHook.

Whether you are building a support-ticket ingestion pipeline, a lead-capture workflow, or an automated document processor, JsonHook gives you a consistent, typed interface to Yandex Mail messages without the fragility of raw SMTP or polling-based API integrations.

How to Forward Yandex Mail to JsonHook

Getting Yandex Mail emails delivered to your webhook takes about five minutes. The process has two parts: creating a JsonHook address via the API, and configuring Yandex Mail to forward a copy of each incoming message to that address.

1. Log in to Yandex Mail and click the gear icon to open Settings.
2. Navigate to Mail collection and forwarding › Email forwarding.
3. Click Add forwarding address, enter your JsonHook inbound address, and click Add.
4. Yandex will send a confirmation email to your JsonHook address. Check your JsonHook event log for the confirmation message, click the link, and then select the forwarding rule and activate it.

Once forwarding is active, every email that arrives in your Yandex Mail inbox (or matches your filter) will be relayed to your JsonHook address, parsed, and delivered to your endpoint as a JSON payload within seconds.

You can create your JsonHook inbound address with a single curl command. Replace YOUR_API_KEY with the key from your dashboard and set webhookUrl to your endpoint:

curl -X POST https://jsonhook.com/api/addresses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "label": "Yandex Mail inbound",
    "webhookUrl": "https://your-app.example.com/webhooks/email",
    "secret": "a-random-signing-secret"
  }'

The response includes your unique @in.jsonhook.com address. Copy that address and paste it into the forwarding field in your Yandex Mail settings. That is all the infrastructure you need to stand up.

Yandex Mail vs Yandex Mail IMAP (app password)

When developers first explore email-to-webhook automation they typically discover Yandex Mail IMAP (app password) — the official programmatic route provided by Yandex. The table below shows how it compares to using JsonHook as an intermediary.

The native approach through Yandex Mail IMAP (app password) requires you to set up OAuth credentials or API keys, maintain a long-running listener or polling job, write your own MIME parser, and implement your own retry queue. Any one of those steps can become a reliability bottleneck in production.

JsonHook handles all of that infrastructure on your behalf. You get a single HTTPS webhook call with a predictable JSON schema every time a Yandex Mail email arrives — no polling, no credential rotation, no MIME parsing, and no bespoke retry code to maintain.

JSON Payload Example

When a Yandex Mail email is forwarded to your JsonHook address and delivered to your endpoint, the request body looks like the following. All fields are consistently present; optional fields such as htmlBody and attachments are included when the source message contains them.

{
  "id": "msg_01j8xkr4p2vn3q7w",
  "receivedAt": "2026-03-15T14:32:07.412Z",
  "from": {
    "name": "Alice Smith",
    "address": "[email protected]"
  },
  "to": [
    {
      "name": "",
      "address": "[email protected]"
    }
  ],
  "subject": "Your Yandex Mail message subject here",
  "textBody": "Plain-text content of the email body.",
  "htmlBody": "<div>HTML version of the email body.</div>",
  "headers": {
    "message-id": "<[email protected]>",
    "x-mailer": "Yandex",
    "mime-version": "1.0"
  },
  "attachments": [
    {
      "filename": "document.pdf",
      "contentType": "application/pdf",
      "size": 84234,
      "content": "JVBERi0xLjQK..."
    }
  ],
  "spf": "pass",
  "dkim": "pass"
}

The id field is a unique, stable identifier you can use for idempotent processing. The spf and dkim fields reflect the authentication results JsonHook observed when receiving the message, which you can use to enforce additional trust policies in your handler.

Attachment content is standard base64. Decode it with a single call in any language — Buffer.from(att.content, 'base64') in Node.js, base64.b64decode(att.content) in Python, and so on.

PHP handler for Yandex Mail messages forwarded through JsonHook:

<?php
$secret = getenv('JSONHOOK_SECRET');
$rawBody = file_get_contents('php://input');
$sig = $_SERVER['HTTP_X_JSONHOOK_SIGNATURE'] ?? '';
$expected = hash_hmac('sha256', $rawBody, $secret);
if (!hash_equals($expected, $sig)) {
    http_response_code(401);
    exit;
}

$data = json_decode($rawBody, true);
$from = $data['from']['address'];
$subject = $data['subject'];
$body = $data['textBody'];

// Route Cyrillic emails to translation queue
if (preg_match('/[\x{0400}-\x{04FF}]/u', $subject)) {
    // send to translation service...
}
error_log("Yandex: $from | $subject");
http_response_code(200);

Common Yandex Mail to Webhook Use Cases

Yandex Mail is dominant in Russia and widely used across Eastern Europe and Central Asia. Integrating Yandex Mail inboxes into automated webhook workflows is particularly relevant for applications targeting those markets, as well as for international teams that use Yandex infrastructure for specific regions or business units.

• CIS market localisation pipelines: Applications serving the CIS region that receive customer enquiries via Yandex Mail can route those messages to a webhook for automatic language detection, translation, and routing to the appropriate regional support team.
• Russian e-commerce order handling: E-commerce platforms that send order confirmations via Yandex-linked accounts can forward receipt emails to a webhook that updates order status and inventory in real time.
• Multi-region inbox consolidation: Global teams with regional Yandex Mail accounts can forward all inbound messages to a central webhook endpoint for unified inbox monitoring and response-time tracking.
• Automated translation and routing: Forward Cyrillic-script emails from Yandex to a webhook that pipes the text body through a translation API and routes the translated message to the appropriate team member automatically.