OUR TAKE
Best fit: a broad communications API with channel-specific due diligence
Contiguity can be explored when an engineering team wants several communications surfaces from one vendor. That is a vendor-management advantage only after channel-specific capability differences have been modeled. A generic send method should not hide the commercial and operational context.
Separate the API umbrella from the channel
The public site presents text, email, voice, verification and other channels. The general pricing table’s $19.99 Unlimited package lists SMS, MMS and email; leased numbers are separate. It is not an established iMessage subscription price. Ask which endpoint, sender type and account permissions implement the iMessage product for your use case.
Represent fallback as an observed event
If a provider can use more than one channel, your database should preserve the intended channel and the channel actually reported. Confirm which fields provide that evidence instead of inventing a universal payload. An Android recipient’s response can be part of the same business journey without being an iMessage delivery.
Scope the technical trial
Get current authentication, event, lookup and error documentation for the quoted channel. Verify that a delayed reply correlates to the right contact and that a timed-out request can be investigated. Provider promises about perfect delivery or immediate production readiness remain marketing statements here. Evaluate the exact configuration rather than assuming all products share those properties.
The decision in one sentence
Keep it in a broader API evaluation once a documented iMessage-specific configuration and event model are available.
Read the primary sources
These are the provider’s own descriptions. Prices and product claims are dated snapshots, and performance claims are not our test results.