What you get
Turn on charity notifications and TweetStream will send a `charity/added` WebSocket event when it observes a new charity. The event includes the charity ID, name, slug, enabled state, observation time, and available location or tax details. Discord delivery is optional and best effort. Charity events are not stored in history.
Use cases
Community notifications
Notify community operators when a new charity appears without repeatedly checking listings.
Review workflows
Send the addition into an internal review queue before displaying it or taking another action.
Event handling
Store the charity ID and slug so your consumer does not process the same event twice.
Structured records
Pass the name and available location or tax fields into your internal tools.
How it works
- Turn on one setting - Enable charity notifications from your TweetStream account settings.
- Receive the addition - A newly observed charity arrives as a `charity/added` event on your authenticated WebSocket.
- Route it where it belongs - Store the event, notify your community, or send it through your own review rules before anyone acts on it.
Compare your options
Build with TweetStream
Handle `charity/added` events
Read the charity event type and example envelope, including which fields are optional and why consumers should store events they need.
Read the charity event referenceCommon questions
Charity alerts report observed public additions. They are not a general charity API, donation service, or endorsement of any charity. WebSocket quickstart.