---
title: "Voice profiles of the user and the state of the biometric consent"
method: GET
path: "/v1/voice-profiles"
tags: ["content"]
---

# Voice profiles of the user and the state of the biometric consent

`GET /v1/voice-profiles`

## Request

- Base URL: `https://api.audiomap.ai`
- URL: `https://api.audiomap.ai/v1/voice-profiles`
- Auth: HTTP bearer

People recognised by voice across the user's OWN recordings, only with the explicit biometric consent the person gives in the app or the web (an API key cannot grant it). Never returns the voice vectors. With consent, a voice that sounds like a profile appears as a suggested speaker name with `voice` evidence. Free.

## Response `200`

Consent state and profiles

- object
  - `consent` object
    - `status` 'granted' | 'revoked' | 'never' | 'outdated': `outdated`: granted under an older consent text; it must be accepted again in the app or the web and nothing is analysed meanwhile
    - `grantedAt` string, date-time, nullable
    - `revokedAt` string, date-time, nullable
  - `profiles` object[]
    - `id` string, uuid
    - `name` string
    - `confirmedAppearances` integer
    - `voiceSeconds` number
    - `hasVoiceprint` boolean
    - `voiceExcluded` boolean: The owner chose "do not recognise this person": the profile keeps only its name and is never analysed nor matched

## Other responses

- `401`: Missing or invalid API key
- `403`: Your plan does not include the REST API
- `404`: No note with that id belongs to you
- `429`: Too many requests for this API key

---

[API](https://skmtc.dev/audiomap/apis/audiomap-api.md) · [All operations](https://skmtc.dev/audiomap/apis/audiomap-api/llms.txt) · [OpenAPI document](https://skmtc.dev/audiomap/apis/audiomap-api/revisions/0bc0c0fc6cbb?raw)