Docs Logimeter AI API Documentation

API Documentation

Feedback API, Transcription Fail Event API, and Transcription Events Payload (pull) API.

API Documentation

Authentication

All API requests require token-based authentication:

HTTP Header
Authorization: Token YOUR_API_TOKEN

1. Feedback API

POST /v1/transcription/feedback/ Report incorrect AI-extracted fields
Token Auth v1

The Feedback API is designed for partners to flag inaccuracies in call transcriptions. It provides a mechanism to notify the system when specific fields in a transcription were wrong.

By sending a POST request with the callId or uuid and a list of incorrectFields, you are effectively submitting a report that highlights which parts of the transcription need to be refined. This feedback is crucial for our internal team to analyse and improve the logic of our transcription models, ensuring better accuracy for future transcriptions. The API’s response confirms that your feedback has been successfully received and logged for review.

At least one of the callId or uuid is mandatory.

Endpoint: POST https://next.logimeter.com/v1/transcription/feedback/

Single Field Feedback

curl --location 'https://next.logimeter.com/v1/transcription/feedback/' \
--header 'Content-Type: application/json' \
--header 'Authorization: Token YOUR_API_TOKEN' \
--data '{
    "uuid": "e7XXX92f-1X8X-4XX9-8Xff-xxMASKed54",
    "feedback": {
        "incorrectFields": [
            "CallerInformation.Contact_Number"
        ]
    }
}'

Response

{
    "message": "Feedback submitted successfully",
    "feedback_id": 1,
    "flag_type": "Default",
    "call_id": 1431429008,
    "uuid": "e7XXX92f-1X8X-4XX9-8Xff-xxMASKed54",
    "incorrect_fields": [
        "CallerInformation.Contact_Number"
    ]
}

Multiple Fields Feedback

curl --location 'https://next.logimeter.com/v1/transcription/feedback/' \
--header 'Content-Type: application/json' \
--header 'Authorization: Token YOUR_API_TOKEN' \
--data '{
    "callId": 1431429008,
    "feedback": {
        "incorrectFields": [
            "CallerInformation.Contact_Number",
            "CallerInformation.Name"
        ]
    }
}'

2. Transcription Fail Event API

GET /v1/transcription_events_fail/ List failed transcription events
Token Auth v1

The Transcription Fail Event API allows you to retrieve a list of all transcription events that failed. You can access these events by making a GET request to

Endpoint: GET https://next.logimeter.com/v1/transcription_events_fail/

Without Date Filter

Without Date Filter will return all the failed events for the current date.

curl --location 'https://next.logimeter.com/v1/transcription_events_fail/' \
--header 'Authorization: Token YOUR_API_TOKEN'

With Date Filter

curl --location 'https://next.logimeter.com/v1/transcription_events_fail/?from_date=2024-07-24&to_date=2024-07-25' \
--header 'Authorization: Token YOUR_API_TOKEN'

Response

{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "call_id": 1431428897,
      "call_tracking_number": "27129519430",
      "call_start_stamp": "2024-07-24T11:08:42.918759+02:00",
      "call_end_stamp": "2024-07-24T11:09:16.578781+02:00",
      "request_url": "https://next.logimeter.com/dev/null/",
      "status_code": "404",
      "error_message": "

404

", "create_stamp": "2025-07-30T05:29:51.982098Z", "request_json": { "event": "TranscriptionEvent", "company": { "id": 24386, "name": "Mel Call2Lead Co", "reference": "Mel Call2Lead Co", "logimeter_reference": "37be775e-d88f-4240-9519-23a8facf48b1" }, "callDetails": { "uuid": "714598ab-ad24-4313-af66-eee1447aeade", "callId": 1431428897, "CallType": "Call Manager", "tracking_number": { "id": 3193517, "number": "27129519430" } }, "detectedIntents": [ "After Sales" ], "applicablePackages": [ "Inbound Aftersale" ], "TranscriptionDetails": { "packages": [ { "PackageName": "Inbound Aftersale", "PackageFields": { "Sales": { "Deal_Information": {}, "Sales_Information": {} }, "Aftersales": { "Parts": {}, "Warranty_Extention": {}, "Aftersales_Information": {} }, "Agent_Information": { "Name": "Njongo phone", "Surname": "", "Email_Address": "melsa.butterfly@gmail.com", "Contact_Number": "27722275612" }, "Skills_Development": { "Appointment_Type": "Vehicle Viewing", "Appointment_Booked": true, "Appointment_Type_Group": "Sales" }, "General_Information": { "Call_Summary": "The prospect is interested in purchasing a new Honda vehicle. The agent offers a demo model of the Honda Amaze and arranges a viewing for the next day at 9 am in Somerset West. The agent also confirms the vehicle is a comfort auto, and the prospect will handle the car's financing. The call ends with confirmation of the appointment and providing the prospect's contact details ", "Language_Detection": "English" }, "Prospect_Information": { "Name": "Oliver", "Intent": [ "After Sales" ], "Surname": "Bell", "Email_Address": "None", "Contact_Number": "0767199813" }, "Action_Required_Items": { "caller_lead_type": "Hot", "unreasonably_disqualified_lead": false } } } ] } } } ] }

3. Transcription Events Payload API (pull)

GET /v1/transcription_events/payload/?call_id=<call_id> Poll for completed TranscriptionEvent JSON
Token Auth v1

Aggregator fleet API tokens can poll for the same partner TranscriptionEvent JSON that would be POSTed to a webhook. Partners without a callback URL can still pull completed events once processing finishes.

Endpoint: GET https://next.logimeter.com/v1/transcription_events/payload/?call_id=<call_id>

Discover metadata, status values, and polling rules: GET https://next.logimeter.com/v1/transcription_events/

Example request

curl --location 'https://next.logimeter.com/v1/transcription_events/payload/?call_id=1431460839' \
--header 'Authorization: Token YOUR_API_TOKEN'

Discovery endpoint

curl --location 'https://next.logimeter.com/v1/transcription_events/' \
--header 'Authorization: Token YOUR_API_TOKEN'

Response

When the call is authorized and Aggregator AI is enabled, the API returns HTTP 200 with:

FieldWhen
statusAlways — completed, transcribing, failed, or not_found
call_idAlways
reasonTerminal failed and not_found only
event, callDetails, …status is completed only (same shape as webhook body)

Status values

statusAction
completedProcess the event; stop polling
transcribingPoll again
failedStop polling; pipeline finished without a partner payload
not_foundStop polling; not in progress (never queued or ineligible call)

Reason values (terminal only)

reasonstatus
queue_errorfailed
queue_timeoutfailed
partner_payload_emptyfailed
not_queuednot_found
ineligible_callnot_found

Polling contract

  • Start after call end.
  • Poll every 5–15 seconds.
  • Stop on completed, failed, or not_found.
  • Poll for up to 30 minutes after the call; if still transcribing, contact support.
  • A short not_found with reason not_queued may become transcribing once processing starts — keep polling until terminal or max duration.

HTTP errors

  • 404 — Call is not visible to your token (or does not exist).
  • 403 — Aggregator AI is not enabled for the tracking number.

Previously, in-progress and missing-payload cases returned HTTP 404. Clients must use the status field instead of treating 404 as “still transcribing” (breaking change, 2026).