URL encoding of tilde (~) sign

Andrew,

according to RFC 2396 (https://tools.ietf.org/html/rfc2396) :

2.3. Unreserved Characters

   Data characters that are allowed in a URI but do not have a reserved
   purpose are called unreserved.  These include upper and lower case
   letters, decimal digits, and a limited set of punctuation marks and
   symbols.          unreserved  = alphanum | mark        mark        = "-" | "_" | "." | "!" | "~" | "*" | "'" | "(" | ")"       Unreserved characters can be escaped without changing the semantics
   of the URI, but this should not be done unless the URI is being used 
   in a context that does not allow the unescaped character to appear.  

At the same time we do support encoded tilde character. Your issue is most likely not because of a tilde escaping but due to missing or invalid access token provided in "Authorization" header.

Here is the example of successful request I could send:

GET https://platform.devtest.ringcentral.com/restapi/v1.0/account/%7e HTTP/1.1  Accept-Encoding: gzip,deflate  Authorization: Bearer SUFEMD...VKaUxDZ1lyS3pRVHRVVHBRfEFB