Overview
This section gives you a high-level picture of the Grigora Developer Portal and Apps: what they are, what they do, and how you can use them to build integrations and extensions for Grigora.
The Grigora Developer Portal
The Developer Portal is where you manage your integrations with Grigora. After you sign in, you get:
- Dashboard — A home view for your account and quick access to your apps and resources.
- My Apps — Create and manage your apps (see below). Each app is an OAuth 2.0–style integration that can access Grigora APIs and features on behalf of users who authorize it.
- Docs & Tutorials — In-app links to documentation and step-by-step guides (this documentation site expands on that).
You use the portal to register apps, configure credentials and permissions, add embedded scripts, optionally publish to the Grigora App Store, and monitor usage.
What Are Apps?
An app in the Grigora developer ecosystem is a registered integration that:
- Identifies your product — Name, description, icon, and optional store listing so users and the platform can recognize your integration.
- Uses OAuth 2.0 — Users authorize your app; Grigora issues credentials (e.g.
client_id/client_secret) so your backend can obtain access tokens and call APIs on their behalf. - Declares permissions (scopes) — You choose which capabilities your app needs (e.g. read CMS posts, manage directory data, manage embedded scripts). Users see these when they approve your app.
- Can inject scripts — You can define embedded scripts (e.g. analytics, widgets) that are injected into users' sites in a controlled way (placement and script type).
- Can expose a dashboard — You can attach an embedded or external "dashboard" experience so users manage your integration from inside Grigora.
Apps are the central concept: one app = one integration that can use APIs, scripts, and dashboard surfaces.
What Do Apps Do?
Apps let you:
- Integrate with Grigora programmatically — Use OAuth and scoped APIs to read or write CMS content (posts), directory collections and items, and manage embedded scripts.
- Extend sites with scripts — Provide snippets (e.g. tracking, chat widgets) that are installed on users' projects with clear placement (head, body start, body end) and purpose (essential, functional, analytics, advertising).
- Offer a managed experience — Optional dashboard page (embedded or external) so users configure or monitor your integration without leaving Grigora.
- Reach users via the Grigora App Store — With a store listing (name, tagline, description, media, pricing, support links), you can submit your app for review and list it so Grigora users can discover and install it.
So: apps are the way you build, ship, and manage integrations and extensions on Grigora.
Main Features of Apps
| Feature | Description |
|---|---|
| OAuth & credentials | Register redirect URIs and scopes; obtain and rotate client_id / client_secret; implement the authorization code flow to get access tokens. |
| Scopes | Fine-grained permissions: e.g. CMS (read/write/publish posts), Directory (collections, fields, items), Scripts (read, embed, delete). Users consent only to what you request. |
| Embedded scripts | Define scripts per app with type (essential, functional, analytics, advertising) and placement (head, body start, body end). Scripts can be connected to users' projects via the Scripts API. |
| Dashboard page | Attach an embedded iframe URL or an external URL so your integration has a dedicated "dashboard" inside Grigora. |
| Store listing | Name, tagline, description, category, pricing, media, support/docs links. Used for Grigora App Store discovery and review. |
| Versioning & changelog | Track versions and submit changelog when you submit for review (e.g. minor/major) so reviewers and users see what changed. |
| Reviews & ratings | Once listed, users can leave reviews and ratings; you can view and manage them in the portal. |
| Stats | View usage/analytics for your app (e.g. over a time range) to understand adoption and usage. |
How Can Apps Be Used?
Typical use cases:
- Content & marketing tools — Sync or publish content to Grigora CMS, pull posts for display elsewhere, or automate workflows (e.g. from a third-party CMS or marketing platform).
- Directory and data apps — Build tools that read or manage directory collections and items (e.g. listings, forms, custom data).
- Script-based extensions — Provide analytics, chat, consent, or other widgets that run on users' sites via embedded scripts, with clear placement and consent (e.g. analytics/advertising).
- Unified dashboards — Offer a single place (embedded or external) where users configure your integration and see status or reports.
You create an app in the portal, configure its scopes and redirect URIs, then implement your backend (and optional front-end) to use the APIs and scripts your app is allowed to use. When you're ready, you can add a store listing and submit for review to publish to the Grigora App Store.
Next Steps
- Creating an App — In the Developer Portal, go to My Apps and click Create App. Set name, description, redirect URIs, and scopes.
- OAuth — Use the authorization and token endpoints to get access tokens; then call the API with the token.
- Embedded Scripts — In the app detail view, define embedded scripts and their placement so they can be offered to users' projects.
- Store Listing — When you're ready for the Grigora App Store, complete the store listing and Approval process.