misarmail 1.0.0

Official Dart SDK for MisarMail — transactional email, campaigns, leads, CRM. Full API coverage with retry logic.

MisarMail Dart SDK

Official Dart SDK for the MisarMail API — transactional send, campaigns, contacts, templates, automations, deliverability, warmup, monetization and the two AI streams.

Full reference: misarmail.com/docs.

Install

dart pub add misarmail

Auth

Use a MisarMail developer key (msk_…), created at misarmail.com/developers. It is sent as Authorization: Bearer msk_….

Every call is metered against the subscription attached to that key. There is no client-side limit checking — the server decides, and the SDK surfaces its answer.

Quick start

import 'package:misarmail/misarmail.dart';

final mail = MisarMailClient(apiKey: 'msk_your_key');

await mail.email.send({
  'from': {'email': '[e-mail]'},
  'to': [{'email': '[e-mail]'}],
  'subject': 'Hello',
  'html': '<p>Hi there</p>',
});

final contacts = await mail.contacts.list();

Plan limits

Both a spent allowance and a feature that is not on the plan answer 403, carrying code: "plan_limit_exceeded". The SDK keys on that code rather than the status, which is why a refusal is typed correctly even though 403 is otherwise an authorization failure. The SDK raises MisarMailPlanLimitError for either, and does not retry it — retrying cannot help until the allowance resets or the plan changes. Read upgradeUrl to send the user somewhere useful.

GET /plan returns plan, sending (the per-day and per-month email caps), usage — an array with one entry per metered feature, each carrying used, limit and remaining — and upgrade, which is null until a quota is tight. A null limit means unlimited, and remaining is null alongside it rather than 0. Read it before an expensive call rather than discovering the ceiling through a refusal.

The key needs the read or subscription scope.

final plan = await mail.plan.get();

try {
  await mail.campaigns.create({
    'name': 'Blast',
    'subject': 'We just shipped',
    'fromName': 'Your Name',
    'fromEmail': '[e-mail]',
  });
} on MisarMailPlanLimitError catch (e) {
  print('${e.feature} exhausted on ${e.plan}: ${e.upgradeUrl}');
}

Streaming

Two endpoints stream Server-Sent Events. Both sit outside /v1, which the SDK handles for you:

Method	Route
streaming.generateEmail	POST /api/ai/generate-email/stream
streaming.campaignSend	GET /api/campaigns/{id}/send-stream

Frames are unnamed (data: {…}) and the stream ends with data: [DONE], which the SDK consumes rather than handing on. A stream is never retried: replaying one that failed mid-flight would duplicate whatever you had already read.

await for (final chunk in mail.streaming.generateEmail({'prompt': 'a launch email'})) {
  stdout.write(chunk.data['delta'] ?? '');
}

License

MIT — see LICENSE.