AI Agent Skills & Developer API — Now Live

Today we're launching the Aural Developer API — a full REST API that lets you create interviews, add questions, publish links, track sessions, and pull results, all programmatically. Whether you're integrating Aural into an ATS, automating candidate screening, or letting an AI agent run the entire workflow end to end, the API has you covered.

Why a Developer API?

The Aural dashboard is great for designing and reviewing interviews one at a time. But teams running high-volume hiring, user research pipelines, or automated screening need to create dozens (or hundreds) of interviews without clicking through a UI. Developers and AI agents need a clean, predictable interface they can script against.

The Developer API makes Aural a building block you can embed in any workflow — not just a standalone tool.

What You Can Do

The API covers the full interview lifecycle in five steps:

1. Create an interview — POST /api/v1/interviews with a title, description, AI tone, channels, and time limit.
2. Add questions — POST /api/v1/interviews/{id}/questions with open-ended, single-choice, multiple-choice, coding, or whiteboard questions.
3. Publish — POST /api/v1/interviews/{id}/publish to generate a shareable candidate link.
4. Invite candidates — share the link or use POST /api/v1/interviews/{id}/candidates to register candidates programmatically.
5. Get results — GET /api/v1/sessions/{id} returns the full transcript, AI-generated scores, and analysis.

There are 11 endpoints in total covering interviews, questions, sessions, candidates, publishing, and usage tracking. Every endpoint returns consistent JSON with proper error codes.

Built for AI Agents

We didn't just build an API — we made it agent-friendly from the ground up. Aural ships with three layers of machine-readable documentation:

• llms.txt — a concise summary an LLM can ingest in a single prompt to understand what Aural does and how to call it.
• llms-full.txt — comprehensive plain-text API reference with every endpoint, parameter, and response schema.
• SKILL.md — an agent-oriented guide with intent routing, step-by-step workflows, and tips for autonomous operation.

If you're using Cursor, Copilot, or any LLM-powered coding assistant, you can point it at https://aural-ai.com/SKILL.md and it will know how to create interviews, add questions, publish, and retrieve results on your behalf.

Read https://aural-ai.com/SKILL.md and help me integrate Aural.

Authentication & Rate Limits

API keys are created in Settings → API Keys. Each key is scoped to your organization and inherits your plan's limits. Pass it as a Bearer token:

Authorization: Bearer dlv_your_key_here

Rate limiting is set at 60 requests per minute per API key. Usage from the API counts against your organization's plan — interviews created, session time consumed, and AI tokens used all draw from the same pool as the dashboard. You can check your current usage at any time with GET /api/v1/usage.

OpenAPI Spec

A full OpenAPI 3.1 specification is available for code generation, Postman import, or any tooling that reads OpenAPI. It includes LLM-specific extension fields (x-llm-description and x-llm-hint) so AI tools get extra context about each endpoint's purpose.

Example: Create and Publish an Interview in 30 Seconds

# 1. Create the interview
curl -X POST https://aural-ai.com/api/v1/interviews \
  -H "Authorization: Bearer dlv_your_key" \
  -H "Content-Type: application/json" \
  -d '{"title": "Backend Engineer Screen", "aiTone": "PROFESSIONAL"}'

# 2. Add questions (use the interview ID from step 1)
curl -X POST https://aural-ai.com/api/v1/interviews/{id}/questions \
  -H "Authorization: Bearer dlv_your_key" \
  -H "Content-Type: application/json" \
  -d '[{"text": "Design a rate limiter for an API gateway", "type": "OPEN_ENDED"}]'

# 3. Publish and get the candidate link
curl -X POST https://aural-ai.com/api/v1/interviews/{id}/publish \
  -H "Authorization: Bearer dlv_your_key"

That's it. Three requests and you have a live interview link you can send to candidates.

What's Next

This is the first release of the Developer API. We're planning to add webhooks for session completion events, bulk operations for high-volume pipelines, and SDK packages for Python and TypeScript. If you have feedback or feature requests, reach out at support[at]aural.com.

Read the Quick Start guide, browse the API Reference, or jump straight into the OpenAPI spec. Happy building.