# Junior docs

## I want to ask questions about my calls

Connect Junior to Claude or another AI assistant and ask about your own research in plain language — no exports, no pasting transcripts into a chat window. Ask *"what did buyers say about pricing in the Acme diligence?"* and the assistant pulls the calls itself.

You sign in with your own Junior account and the assistant sees exactly what you'd see in the web app. It can read everything you can, and it can add a new call — it can't alter or delete anything that's already there.

**[Best practices →](/mcp-connector)**

Your IT team adds the connector once for the workspace. After that there's nothing to install: [setup instructions](/mcp-connector/setup).

## I want Junior data in another system

Pull calls and transcripts into a warehouse, an internal dashboard, or another product over HTTP. You can also push calls in from a system Junior doesn't integrate with directly.

Authentication is an API key issued to your organization, so it isn't tied to anyone's account and it reaches what the organization has enabled — organization-wide, not one person's view.

**[REST quickstart →](/rest)** · [API reference](/openapi)

## Which one

If a person is asking the questions, the connector. If code is, the REST API.

|  | MCP connector | REST API |
|  --- | --- | --- |
| Sign-in | Your own Junior account, via OAuth | A long-lived API key issued to the organization |
| Sees | What you can already see in the web app | What the organization has enabled |
| Setup | Paste a URL into your AI client | Write code against HTTP + JSON |
| Can write? | Adds a new call, with a separate scope | Creates projects and ingests calls, where enabled |


An organization can use either or both; they're independent.

## Getting access

Both are enabled per organization by the Junior team — there's no self-serve signup. Contact your Junior representative to have your organization switched on, and for the REST API, to be issued a key.