QuickBooks OAuth infrastructure
Manage QuickBooks authentication across many companies from one clean service.
TicoQuickBooks provides a small, focused OAuth layer for QuickBooks Online. Connect multiple company accounts, store tokens centrally, and request a current access token through a simple API when your other systems need it.
What it does
Each company gets its own connection key, such as beach-blend or client-a, so your team can maintain separate QuickBooks tenants without mixing credentials or refresh tokens.
How teams use it
Start OAuth once, store the connection in DynamoDB, then call the token endpoint whenever another service needs QuickBooks access. The service checks expiry and refreshes only when it should.
Named company connections
Use friendly company keys so each QuickBooks company is easy to identify and maintain over time.
Centralized token storage
Keep access tokens, refresh tokens, realm IDs, and expiry data in one DynamoDB-backed service.
Refresh on demand
Return a valid access token without forcing a refresh on every request. Refresh only when the token is expired or near expiry.
Simple integration layer
Give internal tools and automations one stable endpoint for QuickBooks OAuth and token retrieval.
Built for internal systems
A narrow service on purpose.
This app is designed to handle authentication and token lifecycle management, not accounting workflows or QuickBooks business logic.
By isolating OAuth and token storage, other applications can request the access they need without embedding QuickBooks client secrets everywhere.
Whether you are managing three QuickBooks companies or more later, the service keeps each connection separate and predictable.
Why it exists
One place to handle QuickBooks OAuth well.
Your services can request a current access token by company key through one API instead of implementing their own OAuth flow.
Client credentials stay in the auth service while downstream systems use the protected token endpoint.
Each QuickBooks company has a clear connection record with token expiries, realm ID, and refresh history.