Become an Alerter System Developer

You could develop a mobile app that replicates (or exceeds) the features that we have in our website. In this use case you would not need a server infrastructure with a web server and RDMS, because your app will just be a front-end to our API.

However, there is a caveat.

User account management and payments and billing functions are not part of the API, which means the user will still need to register and manage their user account, purchase a payment plan, and manage their billing and invoices via our website.

In this use case, you will need to use the standard oAuth2 authorization process (see our documentation) to obtain an access token for each user.

You could develop a mobile app and/or website that offer all the alerting features that our API allows, as well as manage things such as user management and user payments. In this use case you would need a server infrastructure with a web server and RDMS, because your app will be using our API to provide a subset of the functionality of the app.

You don't need to report to us the number of users that your application has, or the fees that the users pay to use your application.

In this use case, you are our customer, not your users. Our pricing is designed to charge you in accordance with the load that your application places on the API, not the number of users of your application. Naturally, the more users that you have, the higher will be the load on the API, and the higher will be the fees that we charge you.

Our API has two features that allow you to segregate your data, so that you can show to a user only the data that belongs to them, namely:

• You can create a separate Partition resource for each of your users. All creatable resources in the API belong to a specific Partition resource. There is no limit on the number of Partition resources in a user account.
• You can use the dataSegmentCode field that's on all the API resources to store a unique code that tells your application to which of your users that particular resource belongs.
• You can use a combination of both.

With this use case, you are under no obligation to give us credit or to disclose the fact that your application makes use of our API.

Since this use case is clearly a commercial use of our API, you will be subscribing to one of our Bespoke payment plans.

That means:

• You will have full control over the content of the alerts that are sent out.
• Email alerts will be sent from one of your own email addresses and domains.
• SMS alerts will be sent from one of your own telephone numbers.
• Chat alerts will be sent from one of your own chat accounts.

In this use case, you will use only one oAuth2 access token for all the API calls that your application makes. You can use an Account Access Token that you create in your Developer dashboard.

You could develop an app that provides a predefined set of web content monitors, and then you charge users for using your app.

For example, you could set up web content monitors that watch the pages of an online retailer for the appearance of specific items or specific price levels, and then alert your users when those items appear on the web pages.

In this use case, you will use only one oAuth2 access token for all the API calls that your application makes. You can use an Account Access Token that you create in your Developer dashboard.

If you have an application that has nothing to do with alerting services, where you want to be notified if something unexpected happened, something expected did not happen, something crashed or otherwise happened, or something took longer than expected, etc., then you can use our API to send those alerts.

In this use case, you will use only one oAuth2 access token for all the API calls that your application makes. You can use an Account Access Token that you create in your Developer dashboard.

We will never underestimate your ingenuity to come up with many more use cases!

Go forth and develop!

You are free to charge your users as little or as much as you want for the use of your application. That is of no concern to us.

If you use our API as the plumbing of your alerting service, and you handle user registration and billing, then you will earn income from the fees that your users pay to you. In this case you pay us our standard fees based upon the load that your application puts on our API. Your users will not pay us directly.

You could also earn income from our affiliate program. If you require your users to register an account at AlerterSystem.com, pay us directly, and simply use your application as a better front-end than our website, or as a mobile app, then you can redirect them to our service via your affiliate link or you can give them an affiliate discount coupon to enter in our checkout process.

You could also decide to monetize your application using ads.

Important: If you decide to monetize your application, then you must use one of our Bespoke payment plans. Using our Free or Built-In plans for commercial use is against our terms of service.

Our API is not versioned, meaning there is always only one version of the API.

If we need to remove or change existing API endpoints, we will deprecate the API operation, resource, endpoint, or field. Where appropriate, the deprecated item will have a deprecated notice and a sunset date in the JSON-LD and API documentation. Deprecated resources will also have a Sunset HTTP header.

On the sunset date, the deprecated item will be decommissioned.

The API is built on top of API Platform, which means you can quickly scaffold client apps using either the API Platform Client Generator, Microsoft Kiota Code Generator or the OpenAPI Generator.

Sign up for a free user account on our system (or log in if you already have one). Once you're logged in, use Developers in the menu.

Now you can create a new application, read the developer documentation, and use the API playground to familiarize yourself with the API.

Existing developers, log in and use Developers to view your affiliate dashboard.

Please use our normal support channels.