Reference · built on requestConnectorVoice & contact center

JustCall

Calls, texts, contacts, users, numbers, recordings, and AI call data from JustCall, with signed webhooks.

Request accessPricing ↗

About

JustCall is a cloud phone and SMS system sold by JustCall. Its v2.1 REST API at api.justcall.io covers calls, texts, contacts, users and user groups, phone numbers, Sales Dialer campaigns, analytics, and AI call data. Every request carries the API key and secret in the Authorization header. Webhooks sign each delivery with HMAC-SHA256 in the x-justcall-signature header.

Through Fibric, an operator listens for call.completed, call.missed, and jc.call_ai_generated events, reads the call and its AI data, and proposes a note, a rating, a disposition, or a return call. You approve, and each change leaves a record of what it was and why.

This is a reference listing. It documents what Fibric would read from JustCall and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Calls through GET /v2.1/calls with call_info, call_duration, recording, and voicemail_transcription, filtered by agent, direction, type, or date
  • Call events call.incoming, call.answered, call.missed, call.voicemail, call.enters_queue, call.exits_queue, call.completed, and call.updated with queue_position and exit_reason
  • AI call data through GET /v2.1/calls_ai/{id}: transcription, summary, sentiment, call score, moments, action items, and smart chapters
  • Texts through the texts endpoints, plus SMS and WhatsApp events
  • Users, user groups, phone numbers, and contacts, including the blacklist
  • Sales Dialer calls, campaigns, and contacts, with sd.call_completed and sd.call_ai_generated events
  • Account, agent, and number analytics endpoints

Proposed actions

  • Target capability: propose a note, a half-step rating from 0 to 5, or an existing disposition code on a completed call through PUT /v2.1/calls/{id}
  • Target capability: propose a user availability change through PUT /v2.1/users/availability with a configured unavailability reason
  • Target capability: propose an SMS or MMS through the Send SMS/MMS endpoint
  • Target capability: propose adding a contact to a Sales Dialer campaign

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Score and coach from the AI call data

    jc.call_ai_generated signals the data is ready. The operator reads the call score, moments, and coaching insights and proposes a coaching note for the team lead.

    With Coaching Notes

  • Call back a missed caller

    call.missed and call.voicemail events open a promise. The operator drafts the return call for the agent who owns the number and waits for approval.

    With Callback Promise

  • Reach a new lead first

    When a contact lands in a Sales Dialer campaign, the operator proposes the first-touch call and logs the disposition after it completes.

    With Lead Response

  • Keep coverage during the day

    Queue events show calls entering and leaving queues. When waits build, the operator proposes availability changes for named agents, with reasons your settings allow.

    With Intraday Balance

Requirements

  • A JustCall account on the Team plan or above; API and webhook access start there
  • A user who can open APIs and Webhooks in the dashboard to generate credentials and manage Webhook Settings
  • A public HTTPS endpoint that checks x-justcall-signature and x-justcall-request-timestamp on each delivery
  • JustCall AI for the calls_ai data; pass fetch_ai_data to include it in call lists
Authentication
An API key and API secret from the APIs and Webhooks page of your JustCall account, sent together as Authorization: api_key:api_secret on every request.

Limits

  • Hourly and per-minute limits depend on plan: Team 1800 and 30, Pro 3600 and 60, Business 5400 and 90; a 429 names the reset time
  • Webhooks retry up to 5 times, 30 to 90 seconds apart, then the event is recorded as failed and not retried
  • Event order is not guaranteed and duplicates can arrive; call.updated carries only the call id and changed fields
  • PUT /v2.1/calls/{id} works on completed calls only; in-progress calls cannot be updated

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request JustCall ↗

Questions and answers

How are JustCall webhooks signed?
With HMAC-SHA256 using your API secret as the key. The signed string joins the API secret, the URL-encoded webhook URL, the event type, and the x-justcall-request-timestamp value with pipes. Compare your result to x-justcall-signature. Regenerating credentials changes the signatures.
What rate limits apply?
Limits follow your plan. Team allows 1800 requests per hour and 30 per minute, Pro and Pro Plus 3600 and 60, Business and SalesPro 5400 and 90. Responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, X-Rate-Limit-Reset, and burst equivalents. A 429 asks you to wait for the reset.
Can the connector change a call after it ends?
Yes, for completed calls. PUT /v2.1/calls/{id} replaces the note, sets a rating from 0 to 5 in half steps, or applies a disposition code that already exists in your account. Ongoing calls cannot be updated.
Ask about JustCall

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with JustCall through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy