Skip to content

Log a meeting or call

{ "tool": "log_activity", "type": "meeting", "direction": "outbound", "occurredAt": "2026-11-15T10:00:00+01:00",
"durationSeconds": 1800, "subject": "Demo with Acme",
"body": "Attendees: Laura (CEO). Interested in the annual plan. Next step: proposal on Monday.",
"contactIds": ["<laura id>"], "dealIds": ["<deal id>"], "idempotencyKey": "meeting:<calendar event id>" }

Use type: "call" for a call. Linking the contact updates its lastContactedAt and the deal’s lastActivityAt. The calendar event id in the idempotencyKey makes a retry harmless.

{ "tool": "move_deal", "dealId": "<deal id>", "stageName": "Proposal", "idempotencyKey": "move:<deal id>:proposal" }
{ "tool": "update_record", "type": "deal", "id": "<deal id>",
"changes": { "customFieldsMerge": { "nextStep": "Send proposal 2026-11-17" } } }

customFieldsMerge adds or changes that key and leaves the other custom fields alone. If the account defines nextStep as a typed field, the value must fit its type.

Terminal window
curl -s -X POST https://api.mety.ai/api/v1/activities \
-H "Authorization: Bearer $METY_KEY" -H "Content-Type: application/json" \
-H "Idempotency-Key: meeting:CALENDAR_EVENT_ID" \
-d '{"type":"meeting","occurredAt":"2026-11-15T10:00:00+01:00","durationSeconds":1800,"subject":"Demo with Acme","body":"…","contactIds":["'"$CONTACT_ID"'"],"dealIds":["'"$DEAL_ID"'"]}'
curl -s -X POST https://api.mety.ai/api/v1/deals/$DEAL_ID/move \
-H "Authorization: Bearer $METY_KEY" -H "Content-Type: application/json" -d '{"stageName":"Proposal"}'
curl -s -X PATCH https://api.mety.ai/api/v1/deals/$DEAL_ID \
-H "Authorization: Bearer $METY_KEY" -H "Content-Type: application/json" \
-d '{"customFieldsMerge":{"nextStep":"Send proposal 2026-11-17"}}'