Use HLR Lookup with Sokko.

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 CSV or JSON result export as a file reference, selecting the format explicitly. The export may contain sensitive phone data and HLR intelligence; JSON results are sanitized before delivery.

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.

Return metadata and current progress for one HLR batch. Use it to follow an asynchronous batch until status is COMPLETE.

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.

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.

Request a pause in processing one HLR batch and return the provider's success flag. The action does not poll for a status change.

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.

Request to start or resume processing one uploaded HLR batch and return the provider's success flag without polling for completion. Processing sensitive phone data can irreversibly spend credits, so never invoke this action automatically.

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.