Skip to main content
Back to Documentation

Getting Started

Set up Hugin Alerts in under 60 seconds and send your first notification.

Last updated:

What is Hugin Alerts?

Hugin Alerts is a notification inbox for developers and operators. Send events from anywhere—CI/CD pipelines, cron jobs, monitoring scripts, backend services—and get instant push notifications on your phone.

No SDK required. No complex setup. Just a simple HTTP POST request.

Three Simple Steps

1

Download the App

Get Hugin Alerts from the App Store (iOS) or Google Play (Android).

What you'll need:

  • An iPhone or iPad (iOS 15+) or Android device (Android 8+)
  • Push notifications enabled (you'll be prompted during setup)

Note: Hugin Alerts is currently in early access.

2

Copy Your Ingest Key

After tapping "Get started," your unique ingest key appears right away. This is your authentication token—it's permanent and specific to your device.

Using your ingest key:

  • It's a Bearer token—include it in the Authorization header
  • It never expires (unless you regenerate it)
  • Keep it secret—anyone with your key can send notifications to your device
  • One key works across all your systems and projects

Security tip:

Store your ingest key in environment variables or secrets management, not in your code.

3

Send Your First Event

Fire a test notification from your terminal to see it in action.

Test notification
curl -X POST https://api.huginalerts.com/v1/events \
  -H "Authorization: Bearer YOUR_INGEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "system": "production",
    "event": "test",
    "description": "Hello from Hugin!"
  }'

What happens next:

  1. The API receives your event and returns a 201 Created response
  2. Your phone buzzes within 1-2 seconds
  3. The notification appears in your Hugin app with the event details
  4. Tap the notification to see more info or open the linked URL (if provided)

Next Steps

Tips for Success

Start with one system

Don't integrate everything at once. Pick one critical system (e.g., production deploys or error alerts) and add Hugin there first. Get comfortable with it before expanding.

Use meaningful event fields

The system, event, and component fields help you filter and search later. Use consistent naming across your integrations.

Link to relevant dashboards

Use the url field to link to logs, dashboards, or GitHub PRs. Tapping a notification opens the URL directly.

Be selective about what you send

Hugin is for important events, not logs. If you're tempted to send every API request or database query, you probably want a logging system instead.