• Home
• Config V2 Basics
• Config V2 Organisations
• Config V2 Organisation Types
• Config V2 Channels
• Config V2 Installation Groups
• Config V2 Report Schedule Subscribers
• Config V2 Segments
• Config V2 Dial-In Groups
• Config V2 Goals
• Config V2 Goal Groups
• Config V2 Numbers
• Config V2 Custom
• Config V2 Profile
• Config V2 Users
• Config V2 Roles
• Config V2 Visitor Types
• Config V2 Attribution
• Config V2 SIP Phone System
• Config V2 Notifications
• Config V2 Dialplans
• Config V2 Integrations
• Config V2 PPC
• Config V2 DGRP maps
• Config V2 DGRP map items
• Config V2 IGRP Caller Blocks
• Config V2 Caller Insight
• Config V2 Caller Insight for Salesforce
• Config V2 Call Rating
• Config V2 Custom Vocabulary
• Reports V2 Basics
• Reports V2 Installation Groups
• Reports V2 Dial-In Groups
• Reports V2 Triggers
• Reports V2 Triggers (Deprecated)
• Reports V2 Custom
• Reports V2 Metrics
• Reports V2 Call Rating
• Reports V2 Channels
• Reports V2 Organisations
• Reports V2 Organisation Types
• Reports V2 Segments
• Reports V2 Visitors
• Reports V2 Attribution
• Reports V2 Audit
• Reports V2 Currencies
• Reports V2 Goals
• Reports V2 Real Time
• Reports V2 PBX triggers
• Export V2 Invoices
• Event API Basics
• Event API Example
• Event FTP Upload
• Call Events

• Salesforce Events

• Config V2 Oauth2
• Config V2 Scheduled Reports
• Reports V2 PPC
• Config V2 Keyword Spotting
• Reports V2 Call Keywords

Salesforce Endpoints

Infinity’s integration with Salesforce allows outbound messages to be passed from Salesforce back to Infinity.

The “Caller Insight for Salesforce Installation Guide” contains step-by-step examples of setting up a workflow in Salesforce. This API documentation should be viewed as a supplement to that guide, detailing all the available options. Please ask your account manager for a copy of this guide if you do not have one.

Event API

The events API can be used as the basis for goals in Infinity, and to pass data on to other third party systems for analytics, bid management, etc.

The Salesforce Event API is available on the following secure URL:

POST https://api.infinitycloud.com/callback/v1/salesforce/events

Input Format

• The Salesforce Event API is designed as an endpoint for Salesforce outbound messages.
• The Salesforce outbound message will populate the POST data with a SOAP request.
• The available parameters listed below can be supplied using standard HTTP GET arguments.

Response Format

• Successful requests will receieve a response code of 200 and the expected Salesforce SOAP response.
• Unsuccessful requests due to invalid parameters will receive a 400 response code.
• Outbound message delivery status can be tracked in Salesforce, under “Setup > Monitor > Outbound Messages”.

Available Parameters

The parameters listed below allow you to define custom events from Salesforce. Note that all parameters are optional. For standard events you do not need to provide any of these parameters. See the “Caller Insight for Salesforce Installation Guide” for examples.

• igrpField (string) Optional - The Salesforce custom field containing the Infinity IGRP ID.
• vidField (string) Optional - The Salesforce custom field containing the Infinity visitor ID.
• callRefField (string) Optional - The Salesforce custom field containing the Infinity call reference.
• titleField (string) Optional - The Salesforce custom field containing the title of the event.
• act (string) Optional - Action of Event (such as DOWNLOAD, EXIT, TRANSACTION), will default to the documented standard action if not defined.
  • PLEASE NOTE - For custom events, the Action will be required as part of the request.
• dtField (string) Optional - The Salesforce custom field containing the date or datetime of the event. See Event Timestamps
• tz (string) Optional - Timezone for use with date-only fields in dtField. See Event Timestamps
• txvField (string) optional - The Salesforce custom field containing the transaction value, if any. Defaults to “ExpectedRevenue” for opportunities.
• txcField (string) optional - The Salesforce custom field containing the transaction currency code, if any. Defaults to “CurrencyIsoCode” for opportunities.
• txcDefault (string) optional - The three-letter ISO-4217 currency code to use by default for transactions, if not supplied in txcField. Uses your installation’s default currency if no other option is given.

Event Timestamps

The Salesforce Events API will set the event timestamp according to the following rules:

If the dtField is specified, and populated in the outbound message, it will be used as the event timestamp. If the dtField is a full date/time in Salesforce it will include the time of the event. If the dtField is date-only, the time will be set to 23:59:59 on that day, in the timezone specified by tz (defaults to UTC). Timezones use the same format as our Reports API, see Dates and Timezones for details.

If the Salesforce object’s LastModifiedDate is sent with the outbound message, it will be used as the event timestamp.

Lastly, if no date field is recognised or sent with the outbound message, the date/time of when the event was sent into Infinity will be used as the event timestamp. This may differ from the actual timestamp of the event if there is any delay in sending the message.

Call Rating API

The call rating API is used to send call ratings from Salesforce to Infinity. It is available on the following secure URL:

POST https://api.infinitycloud.com/callback/v1/salesforce/callRating

Input Format

• The Salesforce Call Rating API is designed as an endpoint for Salesforce outbound messages.

Response Format

• Successful requests will receieve a response code of 200.
• Unsuccessful requests due to invalid parameters will receive a 400 response code.
• Outbound message delivery status can be tracked in Salesforce, under “Setup > Monitor > Outbound Messages”.

Available Parameters

The parameters below allow you to send a rating for one call. Note that all parameters are optional. For standard events you do not need to provide any of these parameters. See the “Caller Insight for Salesforce Installation Guide” for examples.

• igrpField (string) Optional - The Salesforce custom field containing the Infinity IGRP ID.
• callRefField (string) Optional - The Salesforce custom field containing the Infinity call reference.
• callRatingField (string) Optional - The Salesforce custom field containing the rating for the call.

Lead Enrich API

The lead enrich API receives new (or updated) lead events, extracts the IGRP and visitor IDs, looks up the marketing data for that lead, then pushes the marketing data back into the Lead record within Salesforce. It is available on the following secure URL:

POST https://api.infinitycloud.com/callback/v1/salesforce/leadEnrich

Input Format

• The Salesforce Lead Enrich API is designed as an endpoint for Salesforce outbound messages.

Response Format

• Successful requests will receieve a response code of 200.
• Unsuccessful requests due to invalid parameters will receive a 400 response code.
• Outbound message delivery status can be tracked in Salesforce, under “Setup > Monitor > Outbound Messages”.

Available Parameters

The parameters below allow to populate lead enrich data with additional options. Note that all parameters are optional. For standard events you do not need to provide any of these parameters. See the “Caller Insight for Salesforce Installation Guide” for examples.

• igrpField (string) Optional - The Salesforce custom field containing the Infinity IGRP ID.
• vidField (string) Optional - The Salesforce custom field containing the Infinity visitor ID.
• dtField (string) Optional - The Salesforce custom field containing the date or datetime of the event. See Event Timestamps
• tz (string) Optional - Timezone for use with date-only fields in dtField. See Event Timestamps
• clickMode (string) Optional - Click mode allows data to be populated from first or last land defaulting to last land.
• extraFields (string) Optional - A simple key-value pair parameter, with keys being the Salesforce field names, and values being the Infinity field names that will be used to populate Salesforce, e.g. “&extraFields[MyLeadField__c]=c_gua_cid”.