[GH-ISSUE #152] Twitter DM integration #105

New issue

Closed

opened 2026-02-25 23:41:12 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 23:41:12 +03:00

Owner

Originally created by @thejeshgn on GitHub (Feb 1, 2018).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/152

Twitter DM integration will be awesome to have. Send alerts to user as DM from a standard healthchecks account.

Originally created by @thejeshgn on GitHub (Feb 1, 2018). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/152 Twitter DM integration will be awesome to have. Send alerts to user as DM from a standard healthchecks account.

kerem closed this issue

2026-02-25 23:41:12 +03:00

kerem commented

2026-02-25 23:41:12 +03:00

Author

Owner

@cuu508 commented on GitHub (May 28, 2018):

An option to be notified over Twitter DM sounds good to me too. But, from reading Twitter API docs, it looks like there would be problems with Twitter's API rate limits. If I'm reading the docs correctly, a single account can send 1000 DMs daily. These are further divided into 15-minute buckets, and the effective limit is about 10 messages per 15 minutes from a single account.

When a single healthchecks.io user receives a flurry of notifications, it could quickly exhaust the quota, and then all the other accounts would miss their notifications.

When a message is received from a user you may send up to 5 messages in response within a 24 hour window. Each message received resets the 24 hour window and the 5 allotted messages. Sending a 6th message within a 24 hour window or sending a message outside of a 24 hour window will count towards rate-limiting. This behavior only applies when using the POST direct_messages/events/new endpoint. [1]

Twitter has the above feature to facilitate conversations with bots, where the user initiates and participates in the conversation. But in healthchecks case, the bot would be the one initiating the conversation, so the rate limits would still be an issue.

Using multiple accounts to send DMs would be against Twitter's ToS -- also no good.

If the user authorizes healthchecks to send DMs from their account, then we're good limits-wise, but DMs will show up as sent by the user, not by @healthchecks_io account.

[1] https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event

@cuu508 commented on GitHub (May 28, 2018): An option to be notified over Twitter DM sounds good to me too. But, from reading Twitter API docs, it looks like there would be problems with Twitter's API rate limits. If I'm reading the docs correctly, a single account can send 1000 DMs daily. These are further divided into 15-minute buckets, and the effective limit is about 10 messages per 15 minutes from a single account. When a single healthchecks.io user receives a flurry of notifications, it could quickly exhaust the quota, and then all the other accounts would miss their notifications. > When a message is received from a user you may send up to 5 messages in response within a 24 hour window. Each message received resets the 24 hour window and the 5 allotted messages. Sending a 6th message within a 24 hour window or sending a message outside of a 24 hour window will count towards rate-limiting. This behavior only applies when using the POST direct_messages/events/new endpoint. [1] Twitter has the above feature to facilitate conversations with bots, where the user initiates and participates in the conversation. But in healthchecks case, the bot would be the one initiating the conversation, so the rate limits would still be an issue. Using multiple accounts to send DMs would be against Twitter's ToS -- also no good. If the user authorizes healthchecks to send DMs from their account, then we're good limits-wise, but DMs will show up as sent by the user, not by @healthchecks_io account. [1] https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event

kerem commented

2026-02-25 23:41:12 +03:00

Author

Owner

@cuu508 commented on GitHub (Aug 20, 2018):

Asked about this on Twitter developer forum, and looks like sending quotas would indeed be a problem.

https://twittercommunity.com/t/sending-server-monitoring-notifications-as-dms-and-api-limits/106278

Closing this for now -- if Twitter's rate limit policy changes in future, we'll revisit.

@cuu508 commented on GitHub (Aug 20, 2018): Asked about this on Twitter developer forum, and looks like sending quotas would indeed be a problem. https://twittercommunity.com/t/sending-server-monitoring-notifications-as-dms-and-api-limits/106278 Closing this for now -- if Twitter's rate limit policy changes in future, we'll revisit.