Authorisation
Access limited to the permitted workspace, role and operation.
APIs and evidence
Bring analysis into your tools.
Export authorised reports to share results and context with your team. For connections to other systems, define the data, recipients and frequency: an external API integration requires a specific technical assessment.
What you get
Data includes its meaning.
A company dashboard may need results by brand, market and period; an editorial workflow may need the sources behind a proposal. Start with the available exports and assess any API connection separately with the technical team.
| Outcome | Meaning | How to handle it |
|---|---|---|
| No relevant results | The completed collection found no matches within the intended scope. | Retain the sample and conditions; do not extend the finding to unobserved channels. |
| Access not permitted | The current context does not authorise the read or operation. | Check permissions and rights without returning content from another workspace. |
| Source unavailable | The collection cannot produce a complete, verifiable result. | Show the gap and follow the defined recovery process; do not return a measured zero. |
What you get
Restricted access. Explicit limits.
Agree on fields, quotas and usage rights before integration. Source and date must accompany results outside the workspace too; a subscription does not automatically include a public API or rights to redistribute content.
- Client system identity
- Authorised workspace
- Permitted operation and quota
Data with context
Connect the result. Keep the meaning.
A useful connection to customer systems needs to carry more than a number. The brand, period, origin and method allow another application to interpret the result without guesswork.
The data contract distinguishes observations, aggregates and plans. A mention refers to content; a measurement describes a sample; a proposal concerns an action to assess. Exports and access must respect source rights and workspace permissions. The API scope must be agreed according to enabled capabilities and authorised uses.
| Subject | Context to retain | Intended use |
|---|---|---|
| Observation | Source, collection time and brand attribution. | Connect evidence to an authorised investigation. |
| Measurement | Period, sample, denominator and exclusions. | Read an indicator without extending it to unobserved data. |
| Plan | Version, evidence and review status. | Follow a proposal without confusing it with an executed action. |
Controlled access
The same boundaries, through the API.
An integration must not bypass application rules. The authorised context determines which data can be read and which operations may be requested.
Access for customer systems requires dedicated credentials, documented permissions, quotas and revocation management. Responses must distinguish an empty result from an unavailable source and denied access. Repeated requests must not become duplicate actions: write contracts require specific checks before exposure.
Source rights
Fields and excerpts available only for permitted uses.
Clear outcomes
Documented errors and limits, without confidential content in diagnostic messages.
Verifiable documentation
Examples to test. Limits to understand.
To assess an integration, define example inputs and outputs, permissions and usage limits. Validate the specific use case with the technical team before making it part of everyday work.
API access requires a stated scope of functions, revocable authorisations and defined quotas. Provider rights limit which data may be transferred: access to analysis in the workspace does not automatically grant a redistribution licence.
- Read the data contract
- Test responses and errors
- Check the authorised use
Related paths
Choose your next step.
Check your brand’s presence, compare results or choose content improvements: continue with the feature you need.
Understand reputation. Strengthen trust.
TrustInsider helps you understand where your brand appears in AI answers and search results.
ReadFrom question to action
From the question to checking the outcome: context, sources, hypotheses and action plans in the TrustInsider analytical workflow.
ReadA transparent method, not a black box
TrustInsider’s criteria for interpreting reputation and trust: provenance, samples, reviews and the limits of conclusions.
ReadFind the right answer
Find guides, FAQs and methodology to clarify indicators, coverage and access, with dedicated routes for data requests.
Read