Apps
An App selects an organisation and, optionally, a Site for public V1 requests. Its public app ID is sent in the app-id header. It provides product context; it does not sign a reader in or authorise editorial changes.
A member access token identifies a signed-in reader. Provider credentials authenticate trusted identity, billing or import services. These are separate values with separate responsibilities. See Libraries & SDKs for the public and integration API boundaries.
Get the app ID in Desk
Section titled “Get the app ID in Desk”- Open NewsTeam Desk, choose your organisation and open Settings → Apps (
/org/YOUR_ORGANISATION_ID/settings/apps). You need organisation access to manage Apps. - Use an existing app linked to the intended Site, or choose New App, select the Site, enter a Name and choose Create.
- On the app’s card in the Apps list, choose Copy App ID beside the displayed public identifier. Use that value for
app-idor the SDK’sappIdoption. The edit dialog’s internal Id is a different identifier; use the card’s copy control for V1. - Confirm the Site on the card and ask your project owner for the matching API environment. Production uses
https://api.newsteam.io; use the supplied environment for test apps. The app’s Production setting does not move it to another API host. - Publish the Site and the Pages it should serve, then run the checks below.
If the controls are unavailable to you, ask your organisation administrator to supply the Site app ID and matching API origin.
Check your setup
Section titled “Check your setup”Replace YOUR_APP_ID with the public value copied from the Apps card. Both calls are JSON POSTs:
curl --fail-with-body https://api.newsteam.io/v1/site.get \ -H 'content-type: application/json' \ -H 'app-id: YOUR_APP_ID' \ --data '{}'
curl --fail-with-body https://api.newsteam.io/v1/site.route \ -H 'content-type: application/json' \ -H 'app-id: YOUR_APP_ID' \ --data '{"path":""}'site.get should return the expected Site configuration; site.route with an empty path resolves its homepage. An app/authorisation error usually needs an ID/environment check. A route-not-found error also needs a check of the Site’s published homepage and navigation. Do not substitute a provider API key or reader token for the app ID.
Configure your client
Section titled “Configure your client”The website starter keeps configuration on the server:
NEWSTEAM_APP_ID=your-public-site-app-idNEWSTEAM_API_URL=https://api.newsteam.ioSupply the SDK origin without /v1; the SDK adds the versioned operation path. Route browser operations through a constrained same-origin server endpoint when using this architecture.
The native starter uses EXPO_PUBLIC_NEWSTEAM_APP_ID and EXPO_PUBLIC_NEWSTEAM_API_URL. Public mobile configuration is bundled into the app. Keep provider secrets on a trusted server and issued reader tokens in platform secure storage.
A successful command-line request does not prove browser CORS access. A localhost browser origin must be permitted by the API environment, or use the starter’s local review proxy. Do not disable browser security or embed provider secrets to bypass this restriction.
Apps and integrations
Section titled “Apps and integrations”Apps support public content plus protected reader, profile and subscription operations. They do not expose article publishing, organisation management, imports or long-running editorial automation. Those workflows use Desk and supported integration services, configured by service URL, type ID and provider attributes.
Continue with API recipes or choose a starter.