Dave Gray

Add options useful for APIs with multiple resource groups, and reorganize so JSON modification happens separately from writing out the results. Since last PR: avoided possible `NoneType` comparison near exclude...

Add support for [Recipient Validation endpoint](https://developers.sparkpost.com/api/recipient-validation/) ([blog](https://www.sparkpost.com/blog/next-generation-recipient-validation/) [kb](https://www.sparkpost.com/docs/recipient-validation/getting-started-recipient-validation/))

Add support for the [Events API](https://developers.sparkpost.com/api/events/) ([blog](https://www.sparkpost.com/blog/new-events-api-more-powerful-flexible-events-searching/), [kb](https://www.sparkpost.com/docs/tech-resources/events-api-integration/)) Remove support for [Message Events API](https://developers.sparkpost.com/api/message-events/): > Notice on May 8 2019: We are discontinuing the Message Events API on October 1,...

See `Client.TemplatesContext` for an example.

transmissions api: code examples

1

The only example code showing how to use the Transmissions API is in the tests. Add code examples to documentation.

add "shoot yourself in the foot mode" (send arbitrary json)

2

This will allow use of every API feature, specifically ones that don't have explicit support in the client library yet.

https://www.sparkpost.com/api#/reference/message-events/message-events/samples

https://www.sparkpost.com/api#/reference/recipient-lists/create/samples

message events api: code examples

1

The only example code showing how to use the Message Events API is in the tests. Add code examples to documentation.