The MessageMedia Enterprise Webhooks SDK demonstrates how you can verify webhooks signed and sent to you by MessageMedia.
If you have any questions, comments, or concerns, please join our Slack channel: https://developers.messagemedia.com/collaborate/slack/
Alternatively you can email us at: developers@messagemedia.com
If you discover a problem with the code guide, we would like to know about it. You can raise an issue or send an email to: developers@messagemedia.com
We welcome your thoughts on how we could best provide you with SDKs that would simplify how you consume our services in your application. You can fork and create pull requests for any features you would like to see or raise an issue
To be able to use this SDK, you will need a public key provided by MessageMedia. You can find out how to do this by going through the Signature Key Management documentation. You can then make use of the Signature Key Management PHP SDK to create and manage your keys.
This SDK assumes that you have pre-configured a webhook that sends data to a url. If you haven't done this, you can read about how to set one up in the Webhooks API Documentation or the Webhooks PHP SDK. Alternatively, you can specify a callback_url in the message body of a send message request.
To keep this guide simple and easy to understand, we've used XAMPP to set up a server which will monitor for incoming webhooks. You can setup your own production server and use it instead of the XAMPP one if needed.
Create an empty directory for your project, let’s name it “testApp”. Now, open up your command prompt and clone this repository into the directory created.
The method verifySignature in the SignService class will be used for verification. It takes in the following parameters: * Request line: Http request line to calculate the signature * Date: Date in http header to calculate the signature * Message content: Message content to calculate the signature * Digest type: Digest type to hash Request line + Date + Message content * Cipher type: Cipher type to encrypt the hashed message * Public key: Public key to decrypt the signature * Signature: Signature sent by MessageMedia in http header X-MessageMedia-Signature
You are now ready to test the application. Run the Java application your computer.
If all goes well, you should receive a true response which indicates the verification was a success.
Check out the full API documentation for more detailed information.
Please contact developer support at developers@messagemedia.com or check out the developer portal at developers.messagemedia.com
Apache License. See the LICENSE file.