Qlynk - Get URL icon

Qlynk - Get URL

Retrieves details of a shortened URL. REQUIRED: short_code (string). RETURNS: Complete URL object with short_code, short_url, original_url, title, description, category_id, created_at.

Overview

This node retrieves details of a shortened URL from the Qlynk service using a provided short code. It is useful for scenarios where you need to fetch the original URL and metadata associated with a shortened link, such as verifying link details or displaying link information in an application.

Use Case Examples

  1. Retrieve the original URL and metadata for a given short code to display link details in a dashboard.
  2. Check if a short code is available or already in use by attempting to fetch its details.

Properties

Name Meaning
Short Code The short code of the link to retrieve (the part after qlynk.fr/). This is a required string input used to identify the shortened URL to fetch.

Output

JSON

  • found - Indicates if the short code was found (false if not found).
  • available - Indicates if the short code is available (true if not found).
  • short_code - The short code of the URL (when found).
  • statusCode - HTTP status code of the response, e.g., 404 if not found.
  • message - Message describing the status, e.g., 'Short code is available' if not found.
  • short_url - The full shortened URL.
  • original_url - The original URL that the short code redirects to.
  • title - Title metadata of the original URL.
  • description - Description metadata of the original URL.
  • category_id - Category identifier associated with the URL.
  • created_at - Timestamp when the shortened URL was created.

Dependencies

  • Qlynk API with required API key credentials

Troubleshooting

  • If the 'short_code' parameter is missing or empty, the node throws an error indicating it is required. Ensure this parameter is provided.
  • If the short code does not exist, the node returns a JSON object indicating the short code is available with a 404 status code, which is not an error but an informational response.
  • Network or API errors will cause the node to throw unless 'Continue On Fail' is enabled, in which case errors are returned in the output JSON under an 'error' property.

Discussion