Download the PHP package weble/zohoclient without Composer
On this page you can find all versions of the php package weble/zohoclient. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package zohoclient
Zoho API OAuth Client - PHP SDK
This Library is a SDK in PHP that simplifies the usage of the Zoho Apis, providing a simple client to deal with the OAuth2 implementation, as described here: https://www.zoho.com/accounts/protocol/oauth.html
The library aims to provide you with a streamlined way to generate the access_token you need to call any zoho api you need.
Installation
Example Usages (Offline Mode)
Retrieve the url to authenticate against ZOHO and retrieve the access Token / Refresh Token for the first time
Example Usage (Online Mode)
Modes
Zoho OAuth v2 provides two main ways to obtain an access token:
1) Online
This is the "standard" way used when you need to ask you zoho users to authenticate with their zoho account, and then call the apis on their behalf (ie: as if they were logged in an where quering the apis). This is usually done to login as them and automate some kind of process through the apis, or when you just need a quick access to their profile, for example to login / get their name / get their profile.
The Online mode is the easiest to implement, but generates an access token that expires, usually after 1 hour, so it can't be stored or renewed without a refresh token, that you won't get with this method. After the token expire, you will need to ask your users to login again.
2) Offline
This one is preferred when you need to autonomously renew the access token yourself. Used in all the "machine to machine" communication, and it's the best way when you are using the apis to, for example, sync with a 3rd party application, like your ERP or Ecommerce website.
The offline mode generates both an access token and a refresh token, than you need to store locally, and use it to refresh the access token when it expires.
The library deals with the refresh process automatically, so you don't need to worry about that.
Contributing
Finding bugs, sending pull requests or improving the docs - any contribution is welcome and highly appreciated
Versioning
Semantic Versioning Specification (SemVer) is used.
Copyright and License
Copyright Weble Srl under the MIT license.
All versions of zohoclient with dependencies
psr/cache Version ^1.0 || ^2.0 || ^3.0
league/oauth2-client Version ^2.6
asad/oauth2-zoho Version ^1.0