Ever leaked an API key in a public workspace, and got email spammed by Postman? Did your Postman monitors go haywire in the middle of night, but you were fast asleep and missed the alert? You're not alone.

Lot of companies like Postman use email for alerts, due to its ubiquity and ease of use. But email notifications have some drawbacks:

  1. We get a lot of emails.
  2. Important mails can end up in promotions or spam folders.
  3. Email apps have an uncharacteristic alert sound. All emails sound the same.
  4. You may be asleep.

Missed emails can cost your business. Keeping track of such alerts can be a stressful task, as one needs to look at every incoming email alert.

We faced this problem at work, where we need to respond to e-commerce purchases on our app. We wanted a platform which is reliable, programmable and simple to use. Push notifications fit the bill, but not every developer can have a personal app for their notifications. Postcards app is an elegant solution to this problem.

What it does

Postcards is Twilio for personal push notifications. You can turn your phone into an IoT alarm with a simple API call. You can send postcards

How it works

  1. Install app to get API key. No sign up required!


You can optionally get API key and instructions delivered to your email.


  1. Send Postcard using the REST API. The API key uniquely identifies your device.
  2. Get the alert on your phone!



Use cases

Any place where rapid human action is required, in response to a computer event.

  1. Server meltdowns.
  2. E-commerce purchases.
  3. Your personal burglar, fire, zombie or radiation alarm.
  4. If you are an indie or small developer, this will help you do things that don't scale. Get alerted in real time and do behind the scenes manual work.

Tl:dr- the limit is your imagination.

Sample use cases collection

Look at the sample use cases collection in this workspace for examples.

Pokemon catcher bot

Pokemon caught

We've converted PokeAPI into a Pokemon catcher bot using Postman monitors! Every hour, the bot encounters a random Pokemon. You have a 40% probability of catching the Pokemon. If you are lucky, you'll get a Postcard notifying about your successful catch!


Pokemon type visualizer

After building your dream team, are you looking to challenge the Elite Four? Know your odds by finding what types of Pokemon you have! This uses the GET API to fetch all postcards, and displays them using Postman visualizer API.


Server latency alert

Compliment your Postman latency monitor with a Postcard notification! The test script sends a postcard every time latency is higher than 1000 ms.

High latency

How we built it

  1. A Firebase Cloud Messaging (FCM) token and API key is generated when user installs the app.
  2. User uses the key to access Postcards API. For example, user can send a postcard notification or get a list of his existing postcards.
  3. The postcards API is hosted on cloud functions. Cloud function validates data and calls FCM API to send push notification. The data is also saved in Firestore database, so user can view it.
  4. API documentation is hosted in a Postman public workspace.
  5. Twilio Sendgrid is used to send API key and workspace link to user's email.

Challenges we ran into

  1. Platform fragmentation: We wanted the app to make a customized notification sound. This requires native device APIs, which are different for iOS and Android. I decided to use Android over React Native due to this reason.
  2. Android API compatibility issues: The notification API changed in API 26 (Oreo), where notification channels were introduced. This means version specific code for needed for older and new Android versions.

Tech stack

  1. Firebase cloud messaging (FCM): For push notifications
  2. Firebase cloud functions and Node.js: For compute
  3. Firestore database
  4. Android app: Kotlin, MVVM, Retrofit
  5. Postman public workspaces for API testing and documentation
  6. Twilio Sendgrid for email

Postman features used

  1. Public workspace, collections and requests (GET, POST, PUT, DELETE)
  2. API: Holds OpenAPI 3.0 documentation
  3. Environments: Contains API key and endpoint
  4. Mock servers and test scripts: To check for API uptime, and for Pokemon and latency examples.
  5. Visualization API: For Pokemon example. Used to display Pokemon count per type.
  6. Pre-request script: To generate random number for getting random Pokemon.

Accomplishments that we're proud of

  1. Postcards solves my own problem of missed email alerts. Hopefully the community can also find it useful.
  2. Built and launched my first open-source SaaS.

What we learned

  1. Postman public workspaces are a complete and much better replacement to self-hosted swagger pages. It's an integrated platform for API development, testing and collaboration.
  2. Firebase is a great platform for rapid app development.

What's next for Postcards App

  1. Provide support for older versions for Android.
  2. iOS app.
  3. Explore monetization options like Google Ads and GitHub sponsors. Monetization can be tricky because the app is free and open source.
  4. Start a Discord server and build a developer community around Postcards.
  5. Build a nice website for the app.
  6. Launch on Hacker News and Product Hunt.
Share this project: