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
Explore this link on the map →saved by
related reading
- iMessage, explained - JJTechjjtech.dev
- Lindy – The Ultimate AI Executive Assistantlindy.ai
- Why my macOS Messages badge lied to me (and the one-line fix) - Vox Silvablog.alexbeals.com
- AI Horseless Carriages | koomen.devkoomen.dev
- How we built the v0 iOS app - Vercelvercel.com
- Intercom | The only helpdesk designed for the AI Agent eraintercom.com
- Resend · Email for developersresend.com
- iMessage with PQ3: The new state of the art in quantum-secure messaging at scale - Apple Security Researchsecurity.apple.com
- Notes • Nick Arnernickarner.com
- Kasra on X: "https://t.co/jFAXTHm68Y" / Xx.com
- Nikita Bier on X: "Whenever a team considers adding messaging to their app, I always remind them of the 1970s FedEx tagline: “When it absolutely, positively has to be there.” That’s basically the standard you’re up against. Messaging is thex.com
- intimacies with an iphone - briffin glue hufferbriffinglue.substack.com