• 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

Call Events

If you are a third party telecoms provider and are reselling Infinity Tracking’s services you can use the Call Event API to send real-time call records to be processed.

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

https://ict.infinity-tracking.net/callEvent

Input Format

• Input data needs to be supplied using standard HTTP GET arguments.

Authentication

To access this API you must authenticate with your provider username and password using standard HTTP(S) authentication.

Please contact your account manager if you do not have these credentials.

Response Format

Successful requests will be responded with a 200 response code, unsuccessful requests due to invalid parameters will receive a 400 response code

Parameters

• igrp (int) - IGRP event is associated to
• dt (string) - UTC Datetime of this event, (format: YYYY-MM-DD HH:MM:SS)
• dialledPhoneNumber (string) - Phone number that was dialled
• telcoCallRef (string) - Your internal unique reference for this call
• srcPhoneNumber (string) Optional - Caller’s phone number
• destPhoneNumber (string) Optional - Destination phone number where the call was forwarded to
• callState (string) Optional - Hangup or call progress state
• txr (string) Optional - Transaction Reference (if using CRM integration with Call Reference)
• callDuration (int) Optional - Duration caller’s leg of the call was in answered state (seconds)
• ringTime (int) Optional - Duration caller’s leg of the call was ringing (seconds)
• bridgeDuration (int) Optional - Duration the caller’s leg of the call and destination leg were connected (seconds)