Data fields

When you send a url to Microlink API, the following data fields are detected by default:
  • author (e.g., 'SpaceX')
    A human-readable representation of the author's name.
  • date (e.g., 2018-01-24T18:39:47.000Z)
    An
    ISO 8601
     representation of the date the article was published.
  • description (e.g., 'First static fire test of Falcon Heavy…')
    The publisher's chosen description of the article.
  • image (e.g., https://cdn.instagram.com/…/171196260320789.jpg)
    An image URL that best represents the article.
  • video (e.g., 'https://cdn.instagram.com/…/26867070.mp4')
    A video URL that best represents the article.
  • lang (e.g., en)
    An
    ISO 639-1
     representation of the url content language.
  • logo (e.g., 'https://logo.clearbit.com/instagram.com')
    An image URL that best represents the publisher brand.
  • publisher (e.g., 'Instagram')
    A human-readable representation of the publisher's name.
  • title (e.g., 'Manufactures Advanced Rockets & Spacecraft')
    The publisher's chosen title of the article.
  • url (e.g., 'https://instagram.com/p/BeV6tOhFUor')
    The URL of the article.
When a data field is media content, the following contextual data will be also returned:
  • width: file width in pixels.
  • height: file width in pixels.
  • type: file type extension.
  • size: file size in bytes.
  • size_pretty file size in a human readable format.
Moreover, if the media content is playable (such as video or audio), the following fields will be added as well:
  • duration: source duration in seconds.
  • duration_pretty source duration in a human readable format.
You can customize this behavior via meta and/or data in order to add specific data rules over the target URL.
Additionally, Microlink gives you some HTTP information over the target URL, such as:
  • statusCode: The HTTP status code associated with the url response.
  • headers: The HTTP response headers associated with the url response.
  • redirects: A collection of HTTP redirects, where each entry contains the status code and URL for redirects followed from the original URL.
The service also returns a status field to represent the stage of the current transaction.
You can read format section to know more about that.