npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@alimzen/relayo-sendgrid

v0.1.0

Published

SendGrid driver for Relayo: sending through the v3 API and normalized events from the signed Event Webhook.

Downloads

138

Readme

@alimzen/relayo-sendgrid

SendGrid driver for Relayo: sends through the v3 Mail Send API and turns the signed Event Webhook into Relayo events. No SDK, no runtime dependencies: it uses Node's fetch.

npm install @alimzen/relayo @alimzen/relayo-sendgrid

Sending

import { createRelayo } from '@alimzen/relayo';
import { sendgrid } from '@alimzen/relayo-sendgrid';

const relayo = createRelayo({
  email: sendgrid({
    apiKey: process.env.SENDGRID_API_KEY!,
    webhook: { publicKey: process.env.SENDGRID_WEBHOOK_KEY! },
  }),
});

| Option | | | --- | --- | | apiKey | Required | | region | "eu" for accounts with EU data residency (default "global") | | sandbox | Validate messages without delivering them | | timeoutMs | Request timeout (default 30 000) | | baseUrl, fetch | Override the endpoint or the fetch implementation (proxies, tests) | | name | Provider name in results, events and errors (default "sendgrid") | | webhook.publicKey | Verification key of the Signed Event Webhook (base64, as shown by SendGrid, or PEM) | | webhook.toleranceSeconds | Reject signatures older than this (replay protection). Off by default | | webhook.verifySignature | Set to false to accept unsigned webhooks |

Results have status: 'queued' and the X-Message-Id as providerMessageId. Relayo's messageId and your metadata travel as custom_args, which SendGrid repeats on every event and recipients don't see. Message tags become categories (at most 10). providerOptions are merged into the request body (e.g. { send_at, asm, ip_pool_name }).

| SendGrid answer | Relayo error | Retryable | | --- | --- | --- | | 401, 403 (including an unverified sender) | AuthenticationError | no | | 429 | RateLimitError with retryAfter | yes | | 5xx, network errors, timeouts | ProviderUnavailableError | yes | | Other 4xx (400, 413...) | ValidationError | no |

SendGrid's error list is in error.raw.errors.

Receiving events

  1. In SendGrid, go to Settings → Mail Settings → Event Webhook, set your endpoint URL and choose the events.
  2. Enable Signed Event Webhook and copy the verification key into webhook.publicKey.
  3. Pass each request to Relayo with the raw body: the signature covers the exact bytes, so a body that was parsed and re-serialized won't verify.
app.post('/webhooks/sendgrid', express.text({ type: '*/*' }), async (req, res) => {
  const events = await relayo.handleWebhook('email', { headers: req.headers, body: req.body, rawBody: req.body });
  res.json({ received: events.length });
});

Without a publicKey the driver refuses webhooks with an explicit error, unless you set verifySignature: false.

| SendGrid event | Relayo event | | --- | --- | | processed | accepted | | delivered | delivered | | deferred | deferred | | bounce | bounced | | dropped | rejected (suppressed, invalid_recipient or unknown) | | spamreport | complained | | open / click | opened / clicked (with url) | | unsubscribe, group_unsubscribe | unsubscribed |

group_resubscribe has no Relayo equivalent and is skipped. Bounces are classified from the SMTP status and reason, refined with SendGrid's bounce_classification: Reputation, Content and Frequency or Volume become block even with a 5xx code, and a blocked bounce is never hard. Event ids are SendGrid's sg_event_id.