What Living Security needs
Scopes: CultureAI API keys are not scoped — a valid key grants API access. Living Security only reads reporting data; if your CultureAI console offers scope or permission selection when creating a key, grant read-only reporting access.
Required role: Admin or Owner in CultureAI (to manage API access)
Prerequisites
- You must be signed in to your CultureAI admin console with a role that can manage API access — typically an Admin or Owner role. If you do not see an API or developer settings area, contact your CultureAI account representative to have API access enabled for your organization.
Part A — In CultureAI
Your CultureAI administrator completes these steps.1
Generate an API key
- Sign in to your CultureAI admin console.
- Open your organization or account settings and locate the API (or API keys / Developer) area.
- Create a new API key and give it a descriptive name (e.g.,
Living Security Platform).
Living Security uses this key for read-only access to the reporting data it ingests from CultureAI. No write access is required. If CultureAI prompts you to choose scopes or permissions, grant only read access to reporting data.
If you cannot find where to create an API key, or you are unsure which permissions to grant, contact your CultureAI account representative. Living Security cannot generate CultureAI credentials on your behalf.
Part B — In the Living Security Platform
The program owner completes this step, or the system admin if using delegated setup.1
Troubleshooting
403 Forbidden
403 Forbidden
The API key lacks read access to reporting data. In CultureAI, verify the key is granted read access, or generate a new key with the correct permissions.
Empty results (200 OK but no data)
Empty results (200 OK but no data)
The API key may lack access to the reporting data Living Security ingests. Confirm with your CultureAI account representative that the key has read access to reporting data.

