iMessage API: Three Rewrites, One Apple Ban, and What Actually Works | Lindy
We built iMessage support three times in six weeks. A Swift daemon, a BlueBubbles rewrite, then an API migration after Apple banned our account for sending 10K messages in 12 hours.
iMessage API: Three Rewrites, One Apple Ban, and What Actually Works | Lindy Solutions Log in Sign up Talk to sales Try for free Try for free Try for free Sign up Sign up Sign up Log in Pricing Enterprise Security Integrations Product Templates Integrations App Builder Solutions Use Cases Sales Marketing Operations Support Recruiting Meetings Voice Industry Tech Finance Real Estate Healthcare Resources Docs Case Studies Blog Talk to sales Blog / Agents iMessage API: Three Rewrites, One Apple Ban, and What Actually Works Marvin Aziz Head of Community Marvin is a Growth Engineer at Lindy focused
saved by
related reading
- Communication APIs for Messaging and Voice | Linqlinqapp.com
- Lindy – The Ultimate AI Executive Assistantlindy.ai
- iMessage, explained - JJTechjjtech.dev
- An app can be a home-cooked mealrobinsloan.com
- Shipping at Inference-Speed | Peter Steinbergersteipete.me
- Why my macOS Messages badge lied to me (and the one-line fix) - Vox Silvablog.alexbeals.com
- How I built a sub-500ms latency voice agent from scratch | Nick Tikhonovntik.me
- Ando: Building Slack from Scratch — New Ontologiesnew-ontologies.com
- Ampampcode.com
- Everything I know about good API designseangoedecke.com
- Musings on Building a Generative AI Productlinkedin.com
- Why We Built Our Own Background Agentbuilders.ramp.com