tq share icon

tq share

天启数据

Overview

This node integrates with the Tianqi Data (天启数据) service to retrieve mobile phone numbers and related information. It is particularly useful for scenarios where users need to obtain phone numbers filtered by keywords, channels, operators, or specific number segments. For example, marketing teams might use it to gather valid phone numbers from certain regions or carriers for targeted campaigns, or developers might automate verification processes by fetching phone numbers dynamically.

The "获取手机号" (Get Phone Number) operation allows users to:

  • Search for phone numbers based on a keyword.
  • Select a channel associated with that keyword.
  • Filter numbers by operator type (all, non-virtual, virtual).
  • Specify exact phone numbers or number segments to narrow down results.

Properties

Name Meaning
关键词 (search) Keyword used to search and locate relevant phone number lists. Must be selected from a searchable list.
当前渠道 (remoteOptions) The current channel selected based on the chosen keyword. This determines the source of phone numbers.
运营商 (operator) Operator filter for phone numbers. Options: 全部 (All), 非虚拟 (Non-virtual), 虚拟 (Virtual).
指定号码 (phone_num) Specific phone number to retrieve. Allows fetching a particular number if known.
指定号段 (scope) Specific number segment to query, e.g., numbers starting with "137" or "1371".

Output

The node outputs an array of JSON objects under the json field. Each object contains data returned from the Tianqi Data API about the requested phone numbers. Key fields include:

  • channelId: Identifier of the channel from which the phone number was retrieved.
  • Other phone number details as provided by the API response.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for Tianqi Data service authentication.
  • Makes HTTP requests to the Tianqi Data API endpoints:
    • Base URL: https://api.tqsms.xyz/api
    • Additional endpoint for channel collection: https://web.tqsms.xyz/api/message/RegionCollect/add

Troubleshooting

  • Common issues:

    • Invalid or missing API token will cause authentication failures.
    • Selecting a keyword without available channels may result in empty or error responses.
    • Specifying invalid phone numbers or number segments may return no data.
  • Error messages:

    • Errors from the API are propagated; typical errors include authorization errors or parameter validation failures.
    • If the node is set to continue on failure, errors will be returned as objects with an error code in the output array.
  • Resolutions:

    • Ensure the API key credential is correctly configured and active.
    • Verify that the keyword and channel selections are valid and correspond to available data.
    • Double-check phone number formats and segment inputs.

Links and References

Discussion