How to send a message successfully using the new Gmail REST API?

by

got it!

after reading the RFC 2822 specification I found out, that the complete message needs to be passed in the raw parameter, see the example:

From: John Doe <[email protected]> 
To: Mary Smith <[email protected]> 
Subject: Saying Hello 
Date: Fri, 21 Nov 1997 09:55:06 -0600 
Message-ID: <[email protected]>

This is a message just to say hello. So, "Hello".

So after base64 encoding the complete message, passing it in the raw parameter without using any other parameter, it works fine.

Edit 1:
As @Amit mentioned, it must be web-safe base64 encoded, see also https://code.google.com/p/stringencoders/wiki/WebSafeBase64

So to convert the base64 alpha into a format that is “web-safe” the
following changes are recommended:

+ --> - (char 62, plus to dash)
/ --> _ (char 63, slash to underscore)
= --> * padding

To only convert + to - and /to _ was sufficient for me.

Edit 2:
To answer the question of @Hjulle here an example: you only need the userId and in the request body the raw parameter. Let’s assume, your email address is [email protected]

First Base64 encode the complete message (see above) using an online encoder and you get this string:

RnJvbTogSm9obiBEb2UgPGpkb2VAbWFjaGluZS5leGFtcGxlPiAKVG86IE1hcnkgU21pdGggPG1h
cnlAZXhhbXBsZS5uZXQ+IApTdWJqZWN0OiBTYXlpbmcgSGVsbG8gCkRhdGU6IEZyaSwgMjEgTm92
IDE5OTcgMDk6NTU6MDYgLTA2MDAgCk1lc3NhZ2UtSUQ6IDwxMjM0QGxvY2FsLm1hY2hpbmUuZXhh
bXBsZT4KClRoaXMgaXMgYSBtZXNzYWdlIGp1c3QgdG8gc2F5IGhlbGxvLiBTbywgIkhlbGxvIi4=

Now convert + to - and /to _ and you get

RnJvbTogSm9obiBEb2UgPGpkb2VAbWFjaGluZS5leGFtcGxlPiAKVG86IE1hcnkgU21pdGggPG1h
cnlAZXhhbXBsZS5uZXQ-IApTdWJqZWN0OiBTYXlpbmcgSGVsbG8gCkRhdGU6IEZyaSwgMjEgTm92
IDE5OTcgMDk6NTU6MDYgLTA2MDAgCk1lc3NhZ2UtSUQ6IDwxMjM0QGxvY2FsLm1hY2hpbmUuZXhh
bXBsZT4KClRoaXMgaXMgYSBtZXNzYWdlIGp1c3QgdG8gc2F5IGhlbGxvLiBTbywgIkhlbGxvIi4=

Now pass this in the raw parameter of the API Explorer.

More Related Contents:

  1. What exactly is RESTful programming?
  2. Best practices for API versioning? [closed]
  3. If REST applications are supposed to be stateless, how do you manage sessions?
  4. Free Rest API to retrieve current datetime as string (timezone irrelevant) [closed]
  5. Design RESTful query API with a long list of query parameters [closed]
  6. Transactions in REST?
  7. How to QUEUE a new build using VSTS REST API
  8. What is RESTful programming?
  9. How to understand “RESTful API is stateless”?
  10. API pagination best practices
  11. How to use cURL to send Cookies?
  12. RESTful way to create multiple items in one request
  13. How to construct a REST API that takes an array of id’s for the resources
  14. Firefox Add-on RESTclient – How to input POST parameters?
  15. Spring @ExceptionHandler does not work with @ResponseBody
  16. Why the slow WADL uptake? [closed]
  17. How To Send A Reply With Gmail API
  18. Azure Websites Kudu REST API – Authentication
  19. How to format Swagger 2.0 text descriptions?
  20. Update an entire resource collection in a REST way
  21. What are the best/common RESTful url verbs and actions?
  22. How should the header X-DocuSign-Authentication be used for REST and SOAP?
  23. Restful way for deleting a bunch of items
  24. Swagger documentation with JAX-RS Jersey 2 and Grizzly
  25. How one could use server side sorting and paging with Azure Mobile Services
  26. Can I change the headers of the HTTP request sent by the browser?
  27. When in my REST API should I use an envelope? If I use it in one place, should I always use it?
  28. Swagger UI passing authentication token to API call in header
  29. Hyphen, underscore, or camelCase as word delimiter in URIs?
  30. REST API DESIGN – Getting a resource through REST with different parameters but same url pattern

Leave a Comment