The Fluveo Marketplace lets developers build apps that integrate with merchant accounts. Merchants browse, install, and manage apps directly from their dashboard. Apps connect via OAuth 2.0 and access merchant data through scoped API permissions.Documentation Index
Fetch the complete documentation index at: https://docs.fluveo.com/llms.txt
Use this file to discover all available pages before exploring further.
Two perspectives
For developers
You build the app. Register it withPOST /v1/apps, define the OAuth scopes and redirect URIs it needs, generate client credentials, and submit it for review. Once approved, your app appears in the public marketplace for all merchants to install.
For merchants
You install apps. Browse published apps in the marketplace, review the permissions they request, and install them with a single click. Installed apps can only access the data you explicitly grant.How apps work
Developer registers an app
Create an app via the API or dashboard. Specify a name, description, requested scopes, and redirect URIs.
Developer generates OAuth credentials
Generate a
client_id and client_secret for the app. The secret is shown once — store it securely.Developer submits for review
Public apps must pass a review before appearing in the marketplace. Private apps can be installed directly by the developer’s own merchant account.
Merchant installs the app
The merchant authorizes the app via the OAuth flow, granting specific scopes. An installation record is created and the app receives access tokens.
App distribution types
| Type | Visibility | Review required |
|---|---|---|
public | Listed in the marketplace for all merchants | Yes |
private | Only installable by the developer’s account or via direct link | No (but can be submitted) |
App lifecycle
Every app has astatus field that tracks where it is in the review process:
| Status | Description |
|---|---|
draft | Initial state. The app is being built and configured. |
in_review | Submitted for marketplace review. |
published | Approved and visible in the marketplace. |
rejected | Review failed. The developer can fix issues and resubmit. |
Key resources
| Resource | Description |
|---|---|
| App | The application definition, including name, scopes, and OAuth config. |
| App Installation | A record of a merchant installing an app, with granted scopes. |
| OAuth Client | The client_id / client_secret pair used for the OAuth flow. |
Next steps
- Build an App — Register your app, configure OAuth, and submit for review
- OAuth Flow — Implement the full authorization code flow
- Scopes Reference — See all available OAuth scopes
- App Review Guidelines — Understand what reviewers look for