---
title: API
seoTitle: Argus Archive REST API for Conversations, Transcripts and Alerts
description: Connect your own applications to Argus Archive through secure app registrations: OAuth 2.0, per-app permissions and audit logging, on every plan.
subnav: true
finished: true
---

> [!hero]
> Integrations
>
> # Connect your own applications to *Argus Archive*
>
> The Argus Archive REST API gives your own systems governed access to archived conversations, transcripts, alerts, cases and policies, through app registrations you control.
>
> [Get a demo](/request-a-demo/) [See pricing](/pricing/)

> [!highlights]
> Capabilities
>
> ## What your applications can do
>
> Each app registration reaches only the areas you give it permission for, and reading and changing are separate permissions.
>
> ![](/assets/icons/callrec-icon-call-details.png)
>
> ### Conversations
>
> Search and open archived conversations, with their details, summary, notes and tags.
>
> ![](/assets/icons/callrec-icon-summary.png)
>
> ### Media and transcripts
>
> Play back a conversation's media and read its transcript, each with its own permission.
>
> ![](/assets/icons/callrec-icon-search.png)
>
> ### Keyword and AI search
>
> Find conversations by keyword, by meaning, or both, with filters for date, people, groups, platform and more.
>
> ![](/assets/icons/comprec-icon-failure-alerts.png)
>
> ### Alerts
>
> Read alerts, and update, escalate or close them from your own tools.
>
> ![](/assets/icons/comprec-icon-cases.png)
>
> ### Cases and legal hold
>
> Create and manage cases, add conversations to them, and place or release legal hold.
>
> ![](/assets/icons/comprec-icon-role-access.png)
>
> ### Users, groups and roles
>
> Keep people, groups, roles and named user licenses in step with your other systems.
>
> ![](/assets/icons/comprec-icon-retention.png)
>
> ### Archive and content policies
>
> Manage how long records are kept and what AI review looks for, and test a content policy before you publish it.
>
> ![](/assets/icons/comprec-icon-audit-trail.png)
>
> ### Audit logs
>
> Bring the Argus Archive audit trail into your own monitoring and reporting.

> [!grid]
> Security
>
> ## Secure app registrations
>
> Administrators create an app registration for each application in Argus Archive, and decide exactly what it can do.
>
> ![](/assets/icons/callrec-icon-sign-in.png)
>
> ### Standard OAuth 2.0
> Apps sign in with the OAuth 2.0 client credentials flow and get a signed access token that lasts one hour.
>
> ![](/assets/icons/comprec-icon-own-key.png)
>
> ### Secrets kept safe
> Each client secret is stored in Azure Key Vault and shown only once, when it's created.
>
> ![](/assets/icons/callrec-icon-retention-hold.png)
>
> ### Secrets that expire
> Choose a secret lifetime from 30 days to one year. Argus Archive shows when it's about to expire, and you can generate a new one at any time.
>
> ![](/assets/icons/comprec-icon-enforced-by-policy.png)
>
> ### Only the permissions you give
> Each app gets its own list of permissions, such as reading conversations or closing alerts, applied across your tenant.
>
> ![](/assets/icons/callrec-icon-data-isolation.png)
>
> ### Your data, kept apart
> Each customer has its own database, and an app's token only ever reaches its own tenant.
>
> ![](/assets/icons/callrec-icon-audit-history.png)
>
> ### Audited by name
> Searches, conversation views, playback and most changes made through the API are recorded in the audit log under the app's name.

> [!table]
> Developers
>
> ## Built for developers
>
> A predictable REST API, with a full reference inside Argus Archive.
>
> | Area | Details |
> |---|---|
> | Style | REST and JSON over HTTPS, versioned (v1) |
> | Sign-in | OAuth 2.0 client credentials, one-hour access tokens |
> | Permissions | Per app registration, for each area and action |
> | Lists | Cursor-based pagination |
> | Filtering | Microsoft Graph-style filters, plus keyword, semantic and hybrid search |
> | Rate limits | Per app, with standard `RateLimit` headers and a 429 response |
> | Reference | OpenAPI 3.0, for signed-in users under Docs |
> | Plans | Every plan |

> [!faq]
> FAQ
>
> ## Frequently asked questions
>
> Still have questions? Ask the team that built it.
>
> [Talk to us](/contact/)
>
> ### Who can create app registrations?
> People whose Argus Archive role includes the app registration permissions. The Administrator role has them by default. App registrations are under Administration, in the Integrations section.
>
> ### How do I stop an app?
> Set its app registration to inactive or delete it, and it can't get a new token. A token it already has works until it expires, within the hour.
>
> ### What happens when a secret expires?
> The app can't get new tokens until you generate a new secret and give it to the app. Generating a new secret replaces the old one straight away.
>
> ### Can an app see everything in our tenant?
> Only the areas you give it permission for. Within those areas, an app works across your whole tenant, as it acts for your organization rather than for one person.
>
> ### Can Argus Archive send events to our systems?
> Not yet. Sending alert events to your own systems is coming soon. Today, alerts can be posted to a Microsoft Teams channel, and your systems can read them through the API.
>
> ### Can we import communications through the API?
> No. Communications are captured from your connected platforms, such as Microsoft Teams.
>
> ### Do AI searches use AI credits?
> Yes. Searching by meaning uses your organization's AI credits, the same as searching in Argus Archive.
>
> ### Where is the API reference?
> In Argus Archive, under Docs. Any signed-in user can open it.
>
> ### Can AI agents use the API?
> Yes, and for AI agents the Argus Archive MCP server is usually the better fit.
>
> [See the MCP server](/integrations/mcp/)

> [!cta]
> Ready when you are
>
> ## Connect your applications to Argus Archive
>
> Built by the people who created market-leading compliance recording and archiving products. Talk to us to see the API and app registrations, or to ask about a trial.