[PeterOcansey]

resolves MSD-15016: API endpoints for WhatsApp messages, inbound messages and recipients

Changelist

• Add whatsapp messages endpoint
• Add whatsapp inbound messages endpoint
• Add whatsapp recipient endpoint
• Update tokens
• Add tests

[mailerlite-kritika]

Confidence Score: 4/5

[Medium risk] The account lists no source beyond the diff, so the tests' use of PaginatedResponse fields (links.last, links.next, meta.currentPage) and the Gson models were not checked against the base class. The 2.4.0 to 2.5.0 version bump is not mentioned in the description, though it fits a minor step for added API surface. Risk rests on additive read-only endpoints and a new token scope, with a version bump a revert undoes.

Summary

Adds WhatsApp read endpoints and bumps SDK to 2.5.0

The PR adds read-only builders for WhatsApp messages, items, activities, inbound messages, recipients and templates under ms.whatsapp(). Each pairs with Gson response models and VCR-fixture tests. The whatsapp_read token scope is added to TokenScopes and TokenAddBuilder. The commits since the last review only move the project version in pom.xml and the README install snippets from 2.4.0 to 2.5.0, a minor step that matches the new public API surface. Once merged, a release built from this commit would publish as com.mailersend:java-sdk:2.5.0.

What's good

• Query parameters are URL-encoded consistently across all new builders.
• Each new endpoint has a README section with a usage example, and the table of contents is updated.

Review context · 0/6 commands

• Commands run: none

_{Reviews (3) · Last reviewed commit: "Bump up version and README update" · claude-sonnet-5-5}