Integration Points¶
Askalot exposes three complementary integration surfaces. They share the same platform capabilities and permission model — pick the one that matches how your system talks to Askalot.
| Integration | Best for | Authentication |
|---|---|---|
| Claude (MCP + plugin) | AI agents running the research lifecycle by conversation | OAuth 2.1 browser login |
| REST API | Server-to-server automation, CI, custom applications | Personal API token (X-Api-Token header) |
| Survey Presentation Format | Rendering live surveys inside your own application UI | Same REST credentials |
Claude over MCP¶
Askalot's MCP server lets Claude (Claude.ai, Claude Desktop, Claude Code) manage projects, questionnaires, campaigns, and data analysis directly through conversation. Claude Code users can additionally install the Askalot plugin — skills, slash commands, and the MCP tools in one package. Authentication is an interactive OAuth 2.1 flow; no API keys to manage.
REST API¶
Every platform entity — projects, questionnaires, campaigns, respondents, surveys, bundles, pools, strategies — is available under https://portor.<tenant>.askalot.io/api/v1 with an OpenAPI 3.0 specification and interactive Swagger UI at /api/v1/docs.
Authentication uses a personal API token:
- Log in to
https://roundtable.<tenant>.askalot.ioand open Profile Settings → API Tokens - Generate a token (you choose the expiry; the token is shown only once)
- Send it in the
X-Api-Tokenheader on every request
The token inherits your account's roles and permissions and can be revoked at any time — revocation takes effect immediately. The Authorization: Bearer header on the REST API is reserved for OAuth access tokens (the credential the MCP transport uses); API tokens always travel in X-Api-Token.
Survey Presentation Format¶
Instead of embedding an Askalot-styled survey page, your application can drive a survey session item by item and render each question with its own UI components. Every step arrives as a self-contained JSON document — question caption, input control specification, and valid options — while Askalot's engine keeps the flow logic, branching, and validation server-side.