Download the PHP package hotrush/quickbooks-manager without Composer
On this page you can find all versions of the php package hotrush/quickbooks-manager. 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 quickbooks-manager
QuickBooks Online manager for Laravel
- Manage different connections (credentials)
- Store tokens in the database
- Refresh token automatically
- Functionality for tokens acquiring
- Webhooks management
- Api SDK included
- Logging
Installation
You have to migrate the database
Also you can publish config file
Authorization
To redirect to OAuth authorization page use qbm.redirect route e.g.:
On successful auth token will be stored in the database and used automatically for API requests. You can configure redirect-back route for success authorization in config file changing redirect_route option.
Api requests
When token received you can use connection manager to send api requests. To get manager instance you can use laravel's container resolving stuff and resolve for Hotrush\QuickBooksManager\QuickBooksManager class.
Then just get needed connection and send request.
Webhooks
Each connection has it's own webhook endpoint e.g.
You can also define verifier_token for each connection to verify data received by webhook (read more).
Each webhook's notification will spawn a new laravel's event. You can easily create your own event listener to handle it.
Events list:
Hotrush\QuickBooksManager\Events\EntityCreateHotrush\QuickBooksManager\Events\EntityUpdateHotrush\QuickBooksManager\Events\EntityDeleteHotrush\QuickBooksManager\Events\EntityMergeHotrush\QuickBooksManager\Events\EntityVoid
Each event has next arguments:
connectionnamerealmIdentityName- the name of the entity type that changed (Customer, Invoice, etc.)entityId- changed entity idlastUpdated- carbon-parsed date objectdeletedId- the ID of the entity that was deleted and merged (only for Merge events)
Tokens refresh schedule
Schedule refreshing in App\Console\Kernel. Schedule docs.
Token's database table
Now you can configure token's table name, just change table_name in config file.
