Skip to main content
POST
/
meeting
/
remap
Remap a meeting with new salesforce objects
curl --request POST \
  --url https://api.momentum.io/v1/meeting/remap \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '{
  "source": {
    "id": "<string>",
    "type": "GOOGLE_CALENDAR"
  },
  "meetingDetails": {
    "title": "<string>",
    "startTime": "2023-11-07T05:31:56Z",
    "hostEmail": "jsmith@example.com",
    "momentumMeetingId": 123
  },
  "salesforceRecords": {
    "opportunityId": "<string>",
    "accountId": "<string>",
    "leadId": "<string>"
  }
}'
{
  "accepted": true,
  "requestId": "<string>"
}

Authorizations

​
X-API-Key
string
header
required

API key for authenticating requests

Query Parameters

​
triggerSummary
boolean
default:false

Whether to trigger call summary after remapping

​
triggerAiSignals
boolean
default:false

Whether to trigger AI signals after remapping

Body

application/json
  • Option 1
  • Option 2

Request body for remapping a meeting. Either source or meetingDetails must be provided: Use source when remapping a meeting based on an external system (e.g., Google Calendar, Zoom, Gong, etc.), providing the source identifier and type. Use meetingDetails when remapping a meeting using explicit meeting information (such as title, start time and host) instead of referencing an external source. Choose the option that best matches the available data for the meeting you wish to remap.

​
source
object
required

Source information for the meeting

​
salesforceRecords
object
required

Associated Salesforce record IDs. At least one record ID must be provided.

  • Option 1
  • Option 2
  • Option 3
​
meetingDetails
object

Details about the meeting. If momentumMeetingId is provided, other fields are not needed.

  • Option 1
  • Option 2

Response

Meeting successfully remapped

​
accepted
boolean
required
Example:

true

​
requestId
string
required

ID of the request for tracking purposes