Frequently asked questions

We have added a list of common questions which should provide your first port of call in the event of problem. These are being updated all the time as users report new queries. 

Its easy to recover your password. Attempt to login as usual, but click on the forgot my password text.

Re-enter your username and or email address and we will send you a recovery link. 


You can always check on your available event credits in the management dashboard. We also provide the ability to get your current balance by querying the RESTful API.

For more details on the API goto:

Event interval periods a fully customisable in template. The event period is the unit of time for the period between each event: (supported values: second, minute, hour, day, week, month) 

My-subscriptions is flexible as you could set an event period in multiple ways for example, a day event period. We support the definition of time in any way:  1 day = 24 hour = 1440 minute = 86400 second

For more information: check out support guide. 

When a schedule is started, the client includes a start date (called first_time).  This is a UTC timestamp that sets when the first ACTUAL event should happen. 

For a period of “monthly” the DAY of the first_time (e.g. 1-31) is used so that the monthly ACTUAL events are sent on the same DAY OF MONTH in all cases. 

If the first_time DAY is 31, some months don’t have 31 days!  So the my-subscription will automatically pull forward the event to the last day of the month at that time.  

Here is an example:
Monthly schedule, every month without any pre or post notifications.

The schedule runs first on the last day of month in this case the 31st January 2018 . (My-subscriptions sets the First_time to 31 January 2018 midday UTC.)

Future events will happen on the last day of each month, i.e.  31 Jan, 28 Feb, 31 March, 30 April, 31 May, 30 Jun … etc.

All events would also be generated at the midday UTC time of each day.

Minimum event period is 15 seconds at the moment. My-subscriptions can work much much faster and we have only set this lower limit as we doubt we will receive a response back from a client application any faster.    

The same 15 second minimum is applied to pre notify and post notify periods, regardless of what the actual event period is.

A template is the basis of a schedule.  A template defines how a schedule “operates”, and a schedule is an instance that generates events.  Can have multiple templates, and multiple schedules for the same template.

Yes it is possible to copy a template. The my-subscriptions RESTful API allows for Read template and Write template, so if you want to copy an existing one then you can.  Each template has a unique template ID.  A template does not need to be unique – users can create the same template multiple times, but each has its own ID. 
Please remember a schedule can only exist under ONE template.


Yes- this is possible through the RESTful API. 

If you know the ScheduleID you  can query directly by API (GET /client/{client_ref}/schedule/{schedule_ref}).

If the you do not know the UserID (client_user_id) then they can use a different API (GET /client/{client_ref}/schedule/index?client_user_id=) to get the schedule_ref, then use GET above for all details.

Its easy to stop a schedule that is running, simply delete it and it will stop!

Still not found what your looking for and need help ? 

Click the link below to get in touch and one of our talented team will be in touch very soon.