Skip to main content

neuroflash API

The neuroflash API gives you programmatic access to audience intelligence through digital twins, content generation, brand voice management, and more.

Base URL​

All API requests are made to:

https://app.neuroflash.com/api

Each service has its own path prefix under this base URL:

ServicePath Prefix
Digital Twins/digital-twin-service
Audiences/audience-service
Brand Voice/brand-voice-service
Content Generation/ds-prototypes/content_generation
Model Selection/ds-prototypes/model_selection
Workspaces/workspace-service
Usage/usage-service

What can you build?​

Audience Intelligence with Digital Twins​

Digital twins are AI representations of real demographic personas. You can ask them questions, run surveys across groups, and get human-like responses grounded in demographic data.

  • Browse pre-built demographic groups (Gen Z, Millennials, Gen X, Baby Boomers, Gen Alpha)
  • Chat with individual twins to get persona-specific insights
  • Run group surveys and get aggregated opinions with summaries
  • Use structured output with custom JSON schemas

Content Generation​

Generate text and images using a variety of AI models (GPT, Claude, Gemini, Mistral) with word usage tracking and streaming support.

Brand Voice​

Create, manage, and apply brand voices to ensure consistent tone across all generated content. Import brand voice from URLs, documents, or text.

Workspace Management​

Manage workspaces, team members, invitations, subscriptions, and billing programmatically.

Getting Started​

  1. Quickstart — Make your first API call in under 2 minutes
  2. Authenticate — Learn about OAuth2 client credentials
  3. Follow a guide — Walk through a complete end-to-end flow
  4. Explore endpoints — Dive into specific API endpoints

Request Format​

All requests use JSON. Set the Content-Type header:

Content-Type: application/json

Include your access token in the Authorization header:

Authorization: Bearer YOUR_ACCESS_TOKEN

Response Format​

All responses return JSON. Successful responses return the resource directly. Error responses follow a standard format.

Paginated endpoints return a consistent structure:

{
"data": [...],
"page": {
"size": 20,
"totalElements": 42,
"totalPages": 3,
"currentPage": 1
}
}