![]() For example, RingCentral Sandbox environment is accessible via base URI. If you plan to work with non-production servers you may be required to use other entry points. Please note that for security reasons connection is allowed using only HTTPS protocol to the default HTTPS port 443, so the port can be omitted in the URI. RingCentral production servers are accessible on. Protocol, host and port together constitute the main entry point to access the API. The RingCentral REST API does not use fragments. Not all API resources allow query parameters.Īn optional part separated from the rest by a hash ( #) and that contains additional information redirecting to a secondary resource for example, a section heading of an article identified by the URI. The query string syntax is organized as a sequence of key-value pairs separated by an ampersand. ![]() foo/bar/baz.Īn optional part separated by a question mark (?) and contains additional identification information that is not hierarchical in nature. If omitted, the default value is used for a given protocol.Ī resource identification, typically hierarchical by nature, e.g. The TCP port where the server listens for incoming requests. The networking protocol (http or https protocols are generally used in REST). The URI syntax is represented by the following scheme: The structure of a URI is similar to that of a web page's URL. ![]() Resources and ParametersĮvery entity in the RingCentral API is represented with a certain resource identified by a specific URI. This guide describes the fundamentals of the RingCentral API and is a useful to developers wishing to understand its conventions and usage guidelines. Last updated: Contributors Edit this page
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |