Notifications for Human Ears

Humans can recognize thousands of distinct sounds. The purpose of Vybit is to take advantage of this capability. Each individual sound, i.e., VIBE, that you create or choose is connected to a specific event, or "BIT" of information, ergo, Vybit! :)

Vybit is currently available FREE as a web app, an Android app, and an iOs app. You can sign in to Vybit using an Apple, Google or Facebook account or via an authentication link sent to your email address.

Vybit's navigation bar at the bottom of the screen includes links to the four main pages. Each of those pages is described in detail below. Page content can be filtered by keyword using the search bar at the top. Note that clicking the symbol ANYWHERE in the app will PLAY the sound of the Vybit but will NOT SEND the Vybit.

Page Descriptions:

There are two ways to create a new Vybit. The first method is to search for or create that perfect sound starting on the SOUNDS page. See details of this method under the Getting Started/SOUNDS section above. The second method is to click the "+ vybit" link in the upper right-hand corner of the app and first enter a name for your new Vybit. From there you will choose a sound and then adjust other relevant settings.

Vybit settings are organized into four sections including GENERAL, TRIGGER, NOTIFICATION, and SUBSCRIPTION. Click on the section headers to toggle the desired section settings. Here are the descriptions for each section:

• NAME - The name of the Vybit.
• OFF/ON - Toggles the Vybit off and on. When the Vybit is toggled off, requests made to the TRIGGER URI (see below) will neither trigger the Vybit nor be logged.
• SOUND - The name of the sound assigned to the Vybit. Click the sound name to set or change the assigned sound. Click the to hear the sound. Note that clicking does not trigger the Vyb, it just plays the sound.
• DESCRIPTION - An optional description of the Vybit for internal use and will also appear in the subscription card (see Subscription Settings below for more details).
• DELETE VYBIT - This will permanently delete the Vybit. Any log records for the Vybit will be preserved.

• TRIGGER URI - The URI containing the unique alpha-numeric key that will trigger the Vybit.
• TRIGGER TYPE - There are four trigger types each explained here:
  • webhook - This is the default trigger type where the Vybit will be triggered by an external service using the TRIGGER URI.
  • integration - this setting indicates the vybit will be triggered by one of the supported automation platforms, i.e., IFTTT, Zapier, Make and Integrately. Setting the trigger type to this value will display convenient links to those platforms.
  • schedule - Vybits with this trigger type will be sent according to a specified time schedule. Click on the SCHEDULE widget (reading "click here to set" if new) to open the schedule editor. From there you can add one or more schedules by configuring the repeating frequency (daily, weekly, monthly, yearly, or interval), the time(s), and the timezone, then clicking "+ ADD". Each saved schedule will appear as a read-only row in the list above the form. To remove a schedule click the × button on the corresponding row. Close the editor when finished.
  • reminders - Vybits with this trigger type will be sent at specific one-time dates and times that you specify. Click on the REMINDERS widget (reading "click here to set" if new) to open the reminder editor. Set the date, time, timezone, and optionally a message, image URL, or link URL, then click "+ ADD". Each saved reminder will appear as a read-only row in the list above the form. To remove a reminder click the × button on the corresponding row. Reminders are automatically cleaned up after they fire.
  • geofence - Vybits with this trigger type will be sent when the device enters or exits a specified area. To set up the geofence click the geofence widget (reading "click here to set" if new) and then follow the instructions below the widget where you will specify the location, radius, type (enter or exit), reset time, and the "devices allowed" settings. If "devices allowed" is set to "only my devices" (the default) then the geofence is only set on your device. Your subscribers will be notified when YOU trigger the geofence, e.g., a Vybit to which your family subscribes to know when you are 5 minutes away from home. If set to "allow subscriber devices" the geofence will also be set the devices of people who subscribe to the Vybit. In this case the Vybit notification is sent ONLY to the particular device that triggers the geofence, e.g., to notify patrons near your business about a special you have going.
• RUN ONCE - When toggled on, the Vybit will automatically turn off after the notification is received. This is useful for one-shot webhooks or any scenario where the Vybit should only fire once. RUN ONCE can also be sent as a parameter in a trigger request POST payload (see "Triggering Vybits" below).

• MESSAGE - an optional default message to send with the notification. This can be overridden with a "message" POST payload. See the "Triggering Vybits" section below for details.
• IMAGE URL - an optional default image to attach to the notification. Must be a direct link to a .jpg, .jpeg, or .png file under 1MB. This can be overridden with an "imageUrl" POST payload. See the "Triggering Vybits" section below for details.
• LINK URL - an optional redirect url when the Vybit notification is tapped. This can be overridden with a "linkUrl" POST payload. See the "Triggering Vybits" section below for details.
• SEND VYBIT - Clicking will manually trigger the Vybit. This is great for testing and sending the Vybit to all of the subscribed PEEPS.

• SUBSCRIPTION LINKS - publish or share these links so that others can subscribe to your Vybit. There is a DIRECT link to the subscription process as well as a CARD link to a subscription presentation page on the Vybit website. See the "Sharing Vybits" section below for more details on how to allow PEEPS (people) to follow your vybits.
• SUBSCRIPTION ACCESS - Controls which people, a.k.a. PEEPS (see below), can subscribe to your Vybit. Set to "Public" to make your Vybit findable under the SUBSCRIBE tab on the VYBITS page (requires approval, see the MODERATION setting description below). Set to "Private" to restrict to only PEEPS you invite. Set to "Unlisted" to allow anyone who is provided with the SUBSCRIPTION LINKS to subscribe (does not require moderation).
• MODERATION - This setting appears when the SUBSCRIPTION ACCESS is set to "Public". Read the PUBLIC ACCESS REQUIREMENTS. Once all of the Vybit settings are finalized click the "Submit for Review". You will be notified when the Vybit has been approved or rejected for public access.
• PEEPS - The number of folks who are subscribed to your vybit. For "Private" ACCESS vybits, click PEEPS to invite and manage the existing invitations and subscribers. See the "Sharing Vybits" section below for more details.

Creating a new Vybit will generate a TRIGGER URI under the Trigger Settings for that Vybit and set the TRIGGER TYPE to "webhook" by default. For example:

 https://vybit.net/trigger/07ygvljzoux6f97x

where "07ygvljzoux6f97x" is the unique API trigger key for this example Vybit. NOTE: Keep the TRIGGER URIs of your vybits private, do not publish or distribute them unnecessarily. For authenticated triggering options using API keys or OAuth2, see the "Developer Portal, Tools, and Service Integrations" section below. Other TRIGGER TYPEs include "integration", "schedule", "reminders", and "geofence". See the "Vybit Creation and Management" section above for more details about the TRIGGER TYPEs.

There are many ways to trigger a Vybit. Here are some of the more common implementations:

• Click the SEND VYBIT button in the Vybit's NOTIFICATION settings view. This is a good way to test the Vybit or manually send the Vybit to all of its subscribers.
• Copy and paste the TRIGGER URI into a new browser tab. This is another easy way to test the Vybit and view the response for the trigger request.
• Use the TRIGGER URI in an outgoing webhook that is provided by another service or platform, e.g., RMMs such as NinjaRMM or Pingdom, or API integration platforms such as Blendr or Automate.io.
• Within an applet on IFTTT. Vybit is an official action service there. Choose from a drop down list of your vybits for the action.
• Within a Zap on Zapier. Vybit is an official action app there. Use one of the available Zap templates or integrate the "Send Vyb" action into your own Zaps where you choose from a drop down list of your vybits.
• Within a scenario on Make. Vybit is an official integration app there. Choose from a drop down list of your vybits for the action.
• Within an automation on Integrately. Vybit is an official app there and they have over 100 Vybit automations already pre-built!
• On a specified schedule. Set the Vybit TRIGGER TYPE to "schedule" and add one or more recurring schedules with the desired frequency, time(s), and timezone.
• At a specific date and time. Set the TRIGGER TYPE to "reminders" and add one or more one-time reminders with a date, time, and timezone. Optionally include a message, image, or link.
• When you move in or out of a specified location. Set the TRIGGER TYPE to "geofence" and specify the location and radius to create a perimeter to trigger the Vybit.
• Directly from a server, container, or CI/CD pipeline. The simplest trigger is a single curl command:

    curl -s https://vybit.net/trigger/a7ux4905io5c2iz2

  Include a dynamic message via POST:

    curl -s -X POST https://vybit.net/trigger/a7ux4905io5c2iz2 \
      -H "Content-Type: application/json" \
      -d '{"message": "Deploy to production complete"}'

  Combine with cron for automated monitoring:

    # check disk usage every hour — alert if over 96%
    0 * * * * USAGE=$(df --output=pcent /data2 | tail -1 | tr -d '%% '); \
      [ "$USAGE" -gt 96 ] && curl -s -X POST https://vybit.net/trigger/a7ux4905io5c2iz2 \
      -H "Content-Type: application/json" -d "{\"message\":\"/data2 at ${USAGE}%%\"}"
  
    # alert if nginx goes down
    * * * * * systemctl is-active --quiet nginx || \
      curl -s https://vybit.net/trigger/l2y8isa16jymdfi3

• Direct Integration into your platform, service, or app. You can programmatically send vybits. Making a GET or POST https request to the TRIGGER URI will send the Vyb, e.g.,

   GET https://vybit.net/trigger/07ygvljzoux6f97x

  Successfully triggered vybits will have a JSON formatted response like this:

    Status 200 OK
  
    {
       "result" : "1",
       "plk":"a9n4qfs9jqu2j95n"
    }
  

  Where the plk is a unique identifier for the trigger event. If the Vybit is turned off the response will be this:

    Status 201 OK
  
    {
         "result":0,
         "warn":"vybit 07ygvljzoux6f97x is off and will not be triggered"
    }
  

  If a request with an invalid trigger key is made the response will be this:

    Status 404 Not Found
  
    {
       "result":0,
       "warn":"07ygvljzoux6f97z is invalid"
    }
  

  Dynamic content can be included in a POST Vybit trigger request that will be displayed in the notification and/or the Vybit log. Valid POST JSON payload parameters are message, imageUrl, linkUrl, log, and runOnce. For example:

    POST https://vybit.net/trigger/07ygvljzoux6f97x
  
    Headers:
      Content-Type: application/json
  
    Body JSON Payload:
  
       {
  
          "message" : "for example, this content will override the default Vybit MESSAGE setting and appear in the Vybit LOG",
  
          "imageUrl" : "https://an.image.to.attach.to.the.notification/will_override_the_default_setting.png",
  
          "linkUrl" : "https://a.redirect.url.when.the.notification.is.tapped/will_override_the_default_setting"
  
          "log" : "for example, this content will append the Vybit LOG content and supports <a href='http://link_out_to_somewhere.com' target='_nowhere'>hyperlinks</a>!",
  
          "runOnce" : true   // automatically turn off this Vybit after the notification is sent
  
       }
  

You can subscribe to vybits created by others that are publicly available. For example here are two "house" vybits that you can subscribe to right now:
 

Click HERE to see a full list of searchable, publicly available vybits.

Private vybits can be followed by owner invitation only.

Manage Vybit subscriptions on the VYBITS page by clicking on the "Following" tab or by clicking the Vybit name on the LOG page. From there you can temporarily turn off the Vybit by toggling the OFF/ON switch or you can permanently unsubscribe from a Vybit by clicking the UNFOLLOW button. The SUBSCRIPTION LINKS are included for the publicly available vybits you are following to make them easy to share with others.

See the "Sharing Vybits" section below to learn how to share your vybits with others.

Other people (a.k.a. PEEPS) can subscribe to your vybits. Newly created vybits will generate a SUBSCRIPTION URI under the SUBSCRIPTION settings, and then you can set the Vybit ACCESS to "public", "unlisted", or "private".

Public access means the Vybit is findable in the publicly accessible, searchable Vybit library under the SUBSCRIBE tab on the VYBITS page. See the VYBITS Page section under GETTING STARTED above for more details.

Unlisted vybits will not be findable, but anyone provided with the SUBSCRIPTION URI will be able to subscribe.

Private vybits require an invitation to subscribe. To invite a PEEP to subscribe to a Vybit, click on the Vybit name from either the VYBITS or LOG page and then click on the PEEPS setting and enter the email address of the PEEP to invite. If the PEEP already has a Vybit account associated with the specified email address, they will see an invitation to subscribe to your Vybit in their LOG. If they do not have a Vybit account for that email address, they will receive an email inviting them to sign into Vybit using that email address or a social media account connected to that email address. Once signed in they can subscribe to your Vybit.

PEEPS subscribed to a private Vybit can be managed from the PEEPS page by removing subscribers and/or invitations by clicking the X to the right of the PEEP's name or email address.

You can also control who can trigger the Vybit and who receives the notifications using the SEND PERMISSIONS setting found under SUBSCRIPTION settings. The default "Only I can send notifications to subscribers" setting means only you can trigger the Vybit and your subscribers will receive the notifications. The "Allow subscribers to send notifications to me" setting enables two-way communication where both you and each individual subscriber can trigger the Vybit and both parties will receive the notification. The "Allow subscribers to send notifications to the entire group" setting allows any subscriber to trigger the Vybit and all subscribers in the group will receive the notification, enabling group broadcast functionality.

Similarly, you can subscribe to others' vybits via the provided SUBSCRIPTION URIs or invitations received in your LOG. You can manage your Vybit subscriptions by clicking the Vybit name from either the LOG or VYBITS page. This will open a Vybit subscription page where you can turn off the Vybit or permanently unsubscribe from it.

Vybit provides a hosted server that lets AI assistants like Claude and ChatGPT manage your vybits and send notifications on your behalf. Once connected, you can use natural conversation to create vybits, trigger notifications, set up reminders, browse sounds, and more.

Claude (claude.ai / Claude Desktop)

1. Open Settings → Connectors
2. Click Add Custom Connector
3. Enter the URL: https://api.vybit.net/v1/mcp
4. You'll be redirected to sign in and authorize with your Vybit account

ChatGPT (chatgpt.com / ChatGPT Desktop)

1. Open Settings → Apps → Advanced Settings
2. Toggle ON Developer Mode, then click "Create app"
3. Fill out the form, setting the MCP Server URL to https://api.vybit.net/v1/mcp
4. You'll be redirected to sign in and authorize with your Vybit account

Once connected, try asking your AI assistant things like "show me my vybits", "create a vybit called Morning Alarm", or "trigger my Server Alert with message CPU at 95%".

Vybit is free for typical individual users. There are no limits on the number of push notifications you can receive, whether from Vybits you own or those to which you are subscribed. For individuals or organizations who need to create more Vybits or send more notifications we offer the modestly priced plans described below. Sign in to my.vybit.net to select a plan that fits your needs.

Free

Create up to 10 Vybits

Send up to

100 Notifications per Day
1,500 Notifications per Month

Bronze

Create up to 20 Vybits

Send up to

200 Notifications per Day
3,000 Notifications per Month

$6/month or $54/year

Silver

Create up to 50 Vybits

Send up to

600 Notifications per Day
9,000 Notifications per Month

$10/month or $90/year

Gold

Create up to 100 Vybits

Send up to

1200 Notifications per Day
18,000 Notifications per Month

$16/month or $144/year

Platinum

Need more?

Contact platinum@vybit.net.

Vybit is an official action channel on seven popular automation platforms:

• IFTTT
• Zapier
• Make
• Integrately
• Pipedream
• viaSocket
• Lindy

Integrations with other platforms are in the works. In the meantime Vybit can easily be used with any integration service that has an outgoing webhooks action channel including these:

• AWS
• Tray.io
• Webvizio
• Splunk
• Funnelkit

For you system administrators and developers Vybit can easily be integrated into your own platform and app notification services. Simply issue an https GET or POST request to the TRIGGER URI of the Vybit in the event logic. See the "Triggering Vybits" section above for more details.

For support, questions, comments, etc., please send an email to support@vybit.net.

Vybit has a Developer Portal where you can register your own applications and services to integrate with Vybit. Sign In to your Vybit account at developer.vybit.net and click on the </> DEV link.

The portal provides:

• API Key – authenticate requests to the Vybit Developer REST API
• OAuth2 – self-service registration so your users can connect their Vybit accounts to your service
• Outbound Webhooks – receive a POST request whenever any of your vybits are triggered, with a payload matching the API log record format
• MCP Server – connect AI assistants like Claude and ChatGPT directly to Vybit

The following tools and SDKs are published on NPM and GitHub:

• @vybit/api-sdk – TypeScript/JavaScript SDK for the Vybit Developer REST API
• @vybit/oauth2-sdk – OAuth2 SDK for user-facing applications and service integrations
• @vybit/mcp-server – Model Context Protocol server for AI assistants (local installation)
• @vybit/cli – Command-line interface with structured JSON output for scripting and automation
• @vybit/n8n-nodes-vybit – Community nodes for the n8n workflow automation platform

More developer tools are in the works including a Vybit plugin for apps. Stay tuned! Email integrations@vybit.net for more information.

Distinguish the notifications you send to your audience using a unique, signature notification sound for your brand! Click HERE to learn more about the Vybit Marketing Channel and try out an INTERACTIVE DEMONSTRATION. Email marketing@vybit.net for more information.