Developer Platform

Build Connected Calling Experiences with the RoboConnect API.

Connect approved softphones, CRM widgets, operations dashboards, and reporting tools to your RoboConnect workspace.

Explore Endpoints Request Integration Support

Platform Base URLhttps://portal.roboconnect.pk

Response FormatsJSON and Inertia page props

API request

GET /api/live-calls

{
  "calls": [
    {
      "direction": "outbound",
      "status": "connected",
      "extension": "39001"
    }
  ],
  "serverTime": "..."
}

Authenticated connection

Use the API only with an approved RoboConnect account

Authentication is session-based and protected by CSRF and origin checks. Never expose credentials or SIP secrets in public frontend code.

Integration Use Cases

Extend RoboConnect into the tools your team already uses.

Support custom agent experiences, operational visibility, and customer workflows.

Custom Softphones

Build an approved desktop, mobile, or browser calling experience using per-agent SIP configuration.

CRM Calling Widgets

Give teams calling context, contact lookup, and follow-up actions inside a CRM workspace.

Live Operations Dashboards

Combine agent presence, live calls, and daily activity for supervisors and wallboards.

Reporting & Quality Workflows

Turn call records, recordings, outcomes, and campaign data into business reporting.

01 / Authentication

Authenticate with a protected browser session

RoboConnect uses Laravel Sanctum session authentication.

Request the login page.Store the session and XSRF cookies and read the current Inertia version.
Submit approved credentials.Send the decoded XSRF token, Inertia version, Origin, Referer, and cookie jar.
Reuse the authenticated session.Keep the Origin header on protected requests and handle session expiry safely.

Session authentication

GET /login

POST /login
Content-Type: application/json
X-Inertia: true
X-Inertia-Version: <current-version>
X-XSRF-TOKEN: <decoded-xsrf-token>
X-Requested-With: XMLHttpRequest
Origin: https://portal.roboconnect.pk
Referer: https://portal.roboconnect.pk/login

{
  "email": "[email protected]",
  "password": "<account-password>",
  "remember": true
}

02 / Endpoint Reference

Core API reference

Availability depends on the features enabled for your RoboConnect account.

Authentication

POST /login

Start an authenticated Sanctum session

Session

GET /api/sip-config

Verify the session and retrieve the current agent SIP configuration

Agents

GET /monitor/live/{companyId}

Read agent roster, presence, daily statistics, live calls, and recent activity

Presence

GET /phone/agent-statuses

Read lightweight online, offline, and DND status maps

Calls

GET /calls/history

Read call detail records through Inertia page props

Calls

GET /calls/recordings/{id}

Download an authorized call recording

Calls

GET /phone/timeline/{id}

Read the activity timeline for an authorized call

Live

GET /api/live-calls

Read active calls and the platform server time

Presence

POST /phone/dnd

Toggle Do Not Disturb for the signed-in agent

Contacts

GET /contacts

Read contacts through Inertia page props

Contacts

GET /integrations/contact-lookup/{number}

Find an authorized contact by phone number

SIP

GET /companies/{companyId}/dialer-info/{userId}

Read richer authorized dialer and brand configuration

03 / SIP Provisioning

Provision an approved softphone securely

Treat every returned password and TURN credential as a secret.

Secret handlingDo not persist SIP passwords, TURN credentials, session cookies, or recording URLs in logs or public repositories.

SIP configuration response

GET /api/sip-config

{
  "sip_username": "ext_39001",
  "sip_password": "<secret>",
  "wss_url": "wss://<approved-host>/wss",
  "transport": "both",
  "extension_number": "39001",
  "ice_servers": [
    { "urls": "stun:<approved-host>" },
    { "urls": ["turn:<approved-host>"], "username": "<secret>", "credential": "<secret>" }
  ]
}

04 / Reporting & Capabilities

Build reports from call detail records

Aggregate authorized call records by agent, day, disposition, or campaign.

Call Recording

Review or process recordings when the account permits it

Call Monitoring

Surface live team activity for authorized supervisors

Campaigns

Connect campaign activity and pending dispositions

Contact Lookup

Match phone numbers with approved customer records

Webhooks

Connect supported account events to business workflows

Inbound Routing

Build experiences around queues, departments, and call flow

05 / Responses

Understand common responses

StatusMeaningRecommended action

200Request completedProcess the returned JSON or Inertia props

302Login or page redirectConfirm the session and follow expected Inertia behavior

401Session not acceptedCheck the cookie jar, Origin header, and account access

419CSRF validation failedRefresh the CSRF cookie and submit the decoded XSRF token

429Too many requestsBack off, respect Retry-After where supplied, and retry gradually

06 / Production Readiness

Production integration checklist

Use a dedicated approved account and least-privilege access
Send Origin, Referer, a normal User-Agent, and the authenticated cookie jar
Never log passwords, session cookies, SIP secrets, TURN credentials, or recording URLs
Respect 429 responses and use bounded polling intervals of 2 to 5 seconds for live calls
Validate company and user identifiers from authenticated portal context
Use HTTPS, secure local storage practices, and explicit logout or session expiry handling
Confirm enabled capabilities before presenting a feature in your app

Developer Support

Planning a custom RoboConnect integration?

Share your integration use case with our team.

Discuss Your Integration