Display caller info from any CRM with Custom Contact Badge
Custom Contact Badge connects JustCall to any external system that has an API. When a call comes in, JustCall queries your endpoint and displays a clickable badge with the caller's name and profile link right inside the dialer. No tab-switching required.
Available on: Team plan or higher
How it works
- A call event triggers (incoming call, outgoing call, dialer view, or log view).
- JustCall sends a POST request with the contact's phone number to your endpoint.
- Your system looks up the contact and returns their details.
- JustCall renders a clickable badge in the dialer with the contact's name and a link to their profile.
If your endpoint does not respond or returns an error, the badge does not appear.
Configure the contact badge
- Go to Integrations in JustCall.
- Click All Integrations and search for Custom Contact Badge.
- Click +Integrate, then Continue Setup.
- Fill in the configuration:
| Field | Description |
|---|---|
| URL | Your endpoint that accepts POST requests. Must be publicly accessible. |
| Platform Name | The label agents see on the badge (e.g., your CRM name). |
| Logo | PNG or JPEG image, max 5 MB. |
- Click Save.
Your URL goes through a security review. JustCall whitelists it within 24-48 hours and sends an email confirmation. Previously whitelisted URLs activate immediately.
API specification
Request
Method: POST
Content-Type: application/json
{
"request_id": "<alphanumeric_request_id>",
"contact_number": "18XXXXXXXX"
}
Expected response
{
"success": true,
"data": {
"contact_name": "John Doe",
"contact_profile_link": "https://mycrm.com/contact/1234",
"contact_email": "john.doe@example.com"
}
}
Only contact_name and contact_profile_link are required for the badge to render. contact_email is optional.
Verify request authenticity
JustCall includes three headers with every request:
| Header | Purpose |
|---|---|
x-justcall-signature | HMAC signature to verify |
x-justcall-signature-version | Signature algorithm version |
x-justcall-request-timestamp | Unix timestamp of the request |
Generate a SHA256 hash using this format:
{API_SECRET}|{ENCODED_REQUEST_URL}|{REQUEST_ID}|{TIMESTAMP}
Compare your computed hash against the x-justcall-signature header value. If they match, the request is authentic.
Things to know
- Your endpoint must respond quickly. Slow responses delay badge rendering.
- If
successisfalseor the data is invalid, the badge will not display. - Configuration is only available on the JustCall web portal. Mobile and desktop apps are not supported.