Apps
Apps in NewsTeam are the public identities used to connect products and read-safe consumers to your organization through the V1 API.
Each app has its own details, permissions, API credentials, and optional site context, giving you a clean way to power websites, apps, partner experiences, and other public products.
Why Apps matter
Section titled “Why Apps matter”-
Connect your Sites Link your Sites and other presentation layers back to your organization so they always receive curated, permissioned content.
-
Provide public read access Apps are designed for public-safe data access. They let your products read from NewsTeam without exposing internal editorial workflows.
-
Carry site context An app can be linked to a specific Site so public requests resolve with the right routing, branding, and audience context.
-
Audit and transparency Track which products are engaging with your content and when their credentials were last used.
-
Partner-facing experiences Provide trusted external products or partner portals with curated, read-safe access without compromising internal workflows.
Typical examples
Section titled “Typical examples”- A website or native app connected via its own NewsTeam app that pulls content dynamically.
- A partner portal with controlled access to curated public content.
- A prototype or product app that needs its own app credentials and site context.
Getting started
Section titled “Getting started”- Create an app in your organization’s Apps area.
- Assign roles and, where needed, link it to the appropriate Site.
- Generate the app key/token and configure the client to call the NewsTeam API.
- Test and monitor usage via your audit views.
Apps are not integrations
Section titled “Apps are not integrations”Apps are not the layer for imports, exports, webhooks, or long-running automation.
Those flows belong to the integration layer and the IO SDK, usually backed by service accounts and organization-level permissions.