Check Phone Status
Run full HLR lookups for 1-80 phone numbers. This processes sensitive phone data and spends credits; optional status features can increase the cost.
HLR Lookup provides phone-number validation, network and portability intelligence, account balance checks, and asynchronous bulk HLR processing.
Run full HLR lookups for 1-80 phone numbers. This processes sensitive phone data and spends credits; optional status features can increase the cost.
Create an empty persistent HLR_V2 batch. Creation has no documented charge and handles no phone data; later uploads persist sensitive phone data, and processing can spend credits.
Permanently delete one HLR batch and its results. This action is irreversible: never invoke it without explicit authorization, and download all needed results before deletion. It does not select a batch automatically.
Download a completed batch's full, unpaginated CSV or JSON result export, including source phone values and sensitive HLR intelligence, as a file reference. Select the required format explicitly.
Return metadata and current progress for one HLR batch. Use it to follow an asynchronous batch until status is COMPLETE.
Return the connected HLR Lookup account's remaining credit balance. This zero-credit read is the approved authentication check and does not process a phone number.
List the connected account's HLR batches with their metadata and progress. The response reports provider offset and limit values, but the API documents no pagination inputs.
Pause processing one HLR batch. This action returns when the command is accepted and does not poll for a status change.
Look up network and mobile-number-portability data for 1-80 phone numbers. This processes sensitive phone data and spends credits; requesting the optional ported date is the only MNP feature that can add a surcharge.
Schedule processing of one uploaded HLR batch at a UTC time. Scheduled processing of sensitive phone data can irreversibly spend credits, so never invoke this action automatically. This action does not poll for processing or completion.
Start or resume processing one uploaded HLR batch. Processing sensitive phone data can irreversibly spend credits, so never invoke this action automatically. This action returns when the command is accepted and does not poll for completion.
Upload a CSV file of sensitive phone data into an empty HLR batch. The provider permits one source upload; repeating it on a populated batch is documented to fail.
Upload 1-100,000 sensitive phone numbers into an empty HLR batch as a compact JSON array. The UTF-8 body must not exceed 2 MiB, and a populated batch cannot be uploaded again.
Validate formatting and original-network information for 1-80 phone numbers without a live HLR lookup. It costs zero credits but still processes sensitive phone data.
The HLR Lookup integration connects your Dench AI CRM directly to HLR Lookup, so agents can read and act on your HLR Lookup data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
14 actions are available for agents to invoke on your behalf. Every call runs through HLR Lookup's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find HLR Lookup and click Connect — you'll authorize access through HLR Lookup's own sign-in flow. No API keys or code required.
Ask an agent to use HLR Lookup in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench HLR Lookup integration connects your AI CRM to HLR Lookup, so AI agents can work with your HLR Lookup data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The HLR Lookup integration currently exposes 14 actions, including Check Phone Status, Create Batch, Delete Batch, Download Batch Results, Get Batch, and Get Credit Balance. Agents invoke them on your behalf from chat or from automations.
No. You connect HLR Lookup from your Dench workspace using HLR Lookup's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through HLR Lookup's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the HLR Lookup connection from your workspace settings at any time.