Update Call Metadata

{
  "call_sid": "<string>",
  "to_phone_number": "<string>",
  "customer_phone_number": "<string>",
  "id": 123,
  "assistant_id": 123,
  "status": "<string>",
  "call_meta": {},
  "assistant_name": "<string>",
  "flow_name": "<string>",
  "duration": 123,
  "started_at": "2023-11-07T05:31:56Z",
  "ended_at": "2023-11-07T05:31:56Z",
  "total_cost": 123,
  "llm_cost": 123,
  "tts_cost": 123,
  "stt_cost": 123,
  "telephony_cost": 123,
  "cost_currency": "<string>"
}

{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}

PATCH

api

calls

{call_id}

metadata

{
  "call_sid": "<string>",
  "to_phone_number": "<string>",
  "customer_phone_number": "<string>",
  "id": 123,
  "assistant_id": 123,
  "status": "<string>",
  "call_meta": {},
  "assistant_name": "<string>",
  "flow_name": "<string>",
  "duration": 123,
  "started_at": "2023-11-07T05:31:56Z",
  "ended_at": "2023-11-07T05:31:56Z",
  "total_cost": 123,
  "llm_cost": 123,
  "tts_cost": 123,
  "stt_cost": 123,
  "telephony_cost": 123,
  "cost_currency": "<string>"
}

{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}

Update the custom metadata associated with a call. This allows you to attach arbitrary data to call records for tracking, analytics, or integration with your systems.

Merge Behavior: New metadata is merged with existing metadata. To remove a field, set its value to null.

Use Cases

CRM Integration: Link calls to customer records, tickets, or opportunities
Campaign Tracking: Tag calls with campaign IDs for attribution
Custom Analytics: Add business-specific data for reporting
Outcome Tracking: Record call outcomes like “appointment_booked” or “sale_completed”

Path Parameters

Parameter	Type	Required	Description
`call_id`	integer	Yes	The internal call ID (not the call SID)

Request Body

Field	Type	Required	Description
`metadata`	object	Yes	Key-value pairs to store with the call

{
  "metadata": {
    "customer_id": "cust_abc123",
    "ticket_id": "TICKET-456",
    "campaign": "spring_outreach_2024",
    "outcome": "appointment_scheduled",
    "custom_field": "any_value"
  }
}

Request Example

curl -X PATCH "https://api.burki.dev/api/v1/calls/101/metadata" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "metadata": {
      "customer_id": "cust_abc123",
      "outcome": "appointment_scheduled"
    }
  }'

Response

Returns the updated call object with the merged metadata.

{
  "id": 101,
  "call_sid": "CAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "assistant_id": 123,
  "assistant_name": "ServiceBot",
  "to_phone_number": "+15551234567",
  "customer_phone_number": "+15559876543",
  "status": "completed",
  "duration": 180,
  "started_at": "2024-01-15T10:00:00Z",
  "ended_at": "2024-01-15T10:03:00Z",
  "call_meta": {
    "customer_id": "cust_abc123",
    "outcome": "appointment_scheduled"
  },
  "total_cost": 0.05,
  "llm_cost": 0.02,
  "tts_cost": 0.01,
  "stt_cost": 0.01,
  "telephony_cost": 0.01,
  "cost_currency": "USD"
}

Error Responses

404 Not Found

{
  "detail": "Call with ID 101 not found in your organization"
}

422 Unprocessable Entity

{
  "detail": [
    {
      "loc": ["body", "metadata"],
      "msg": "field required",
      "type": "value_error.missing"
    }
  ]
}

Examples

Python - Add Customer Info

import requests

def tag_call_with_customer(call_id, customer_id, customer_name):
    response = requests.patch(
        f"https://api.burki.dev/api/v1/calls/{call_id}/metadata",
        headers={"Authorization": "Bearer YOUR_API_KEY"},
        json={
            "metadata": {
                "customer_id": customer_id,
                "customer_name": customer_name,
                "tagged_at": "2024-01-15T10:00:00Z"
            }
        }
    )
    
    return response.json()

Python - Record Call Outcome

def record_call_outcome(call_id, outcome, notes=None):
    metadata = {
        "outcome": outcome,  # e.g., "sale", "no_answer", "callback_requested"
        "outcome_recorded_at": "2024-01-15T10:00:00Z"
    }
    
    if notes:
        metadata["outcome_notes"] = notes
    
    response = requests.patch(
        f"https://api.burki.dev/api/v1/calls/{call_id}/metadata",
        headers={"Authorization": "Bearer YOUR_API_KEY"},
        json={"metadata": metadata}
    )
    
    return response.json()

Node.js - Campaign Attribution

const axios = require('axios');

async function attributeCallToCampaign(callId, campaignId, source) {
  const response = await axios.patch(
    `https://api.burki.dev/api/v1/calls/${callId}/metadata`,
    {
      metadata: {
        campaign_id: campaignId,
        traffic_source: source,
        attributed_at: new Date().toISOString()
      }
    },
    {
      headers: { 'Authorization': 'Bearer YOUR_API_KEY' }
    }
  );
  
  return response.data;
}

Webhook Integration

A common pattern is to update call metadata from your webhook handler:

from flask import Flask, request
import requests

app = Flask(__name__)

@app.route('/webhooks/burki', methods=['POST'])
def handle_webhook():
    event = request.json
    
    if event['event'] == 'call_ended':
        call_id = event['call_id']
        
        # Look up the customer in your CRM
        customer = lookup_customer_by_phone(event['customer_phone_number'])
        
        if customer:
            # Tag the call with customer info
            requests.patch(
                f"https://api.burki.dev/api/v1/calls/{call_id}/metadata",
                headers={"Authorization": "Bearer YOUR_API_KEY"},
                json={
                    "metadata": {
                        "crm_customer_id": customer['id'],
                        "account_type": customer['type'],
                        "lifetime_value": customer['ltv']
                    }
                }
            )
    
    return {'received': True}

Best Practices

Use Consistent Keys: Establish naming conventions for your metadata fields (e.g., customer_id vs customerId)
Keep Values Simple: Store IDs and references rather than large objects. Use your own systems for detailed data.
Timestamp Important Updates: Include timestamps when recording outcomes or status changes.
Don’t Store Sensitive Data: Avoid storing PII, credentials, or other sensitive information in call metadata.

Notes

Metadata is stored as JSON and supports nested objects
There is no size limit enforced, but keep metadata concise
Metadata is included in call exports and analytics
Use the List Calls endpoint to filter calls by supported top-level metadata fields such as customer phone, assistant, status, dates, and call SID.

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

call_id

integer

required

Body

application/json

Request model for updating call metadata.

metadata

Metadata · object

required

Response

Successful Response

Schema for call response.

call_sid

string

required

to_phone_number

string

required

customer_phone_number

string

required

integer

required

assistant_id

integer

required

status

string

required

call_meta

Call Meta · object | null

assistant_name

string | null

flow_name

string | null

duration

integer | null

started_at

string<date-time> | null

ended_at

string<date-time> | null

total_cost

number | null

llm_cost

number | null

tts_cost

number | null

stt_cost

number | null

telephony_cost

number | null

cost_currency

string | null

API Documentation

Assistants

Assistant Phone Numbers

Assistant Documents (RAG)

Voice Cloning

Calls

Messaging

SIP Trunks

Billing

Phone Number Management

Call Data

Organization

Webhooks & System

Campaigns

WebSockets

Tools & Custom Actions

Conversation Flows

Learning & Memory

Use Cases

Path Parameters

Request Body

Request Example

Response

Error Responses

404 Not Found

422 Unprocessable Entity

Examples

Python - Add Customer Info

Python - Record Call Outcome

Node.js - Campaign Attribution

Webhook Integration

Best Practices

Notes

Authorizations

Path Parameters

Body

Response

​Use Cases

​Path Parameters

​Request Body

​Request Example

​Response

​Error Responses

​404 Not Found

​422 Unprocessable Entity

​Examples

​Python - Add Customer Info

​Python - Record Call Outcome

​Node.js - Campaign Attribution

​Webhook Integration

​Best Practices

​Notes

Authorizations

Path Parameters

Body

Response

Use Cases

Path Parameters

Request Body

Request Example

Response

Error Responses

404 Not Found

422 Unprocessable Entity

Examples

Python - Add Customer Info

Python - Record Call Outcome

Node.js - Campaign Attribution

Webhook Integration

Best Practices

Notes