The type of this content. Currently only "http://www.ft.com/ontology/content/Article" is supported.
The body of the content. HTML-compatible XML, enclosed in a <body> tag. This property is not present for live blog article content.
The title of the content. For articles this is the main headline
The author(s) of the content
The date and time the content was first published on www.ft.com, formatted as a string in ISO 8601 format
The date and time the content was last published on www.ft.com, formatted as a string in ISO 8601 format
The URL for the request made to retrieve this content.
A list of URIs that represent the content's brand(s)
true indicates that the content is experienced by the consumer in realtime, such as a live blog post, and the body of the content is not present. For other content this property is not present.
Can be "exclusive", "scoop" and "editorsChoice". They indicate that the content is worthy of special attention. "Scoop" identifies news that is not yet reported by any other media organisations, which only the FT has knowledge of and and is breaking ahead of other news providers. "Exclusive" identifies content only available through the FT (eg interview, comment). Not necessarily a scoop and can be about an event or subject that has been previously reported."EditorsChoice" identifies journalism that our Editorial team wish to highlight because it is worthy of special attention.
Can be "yes", "no" or "verify". If "yes" then if you have a syndication agreement with the FT then this content may be available to syndicate, subject to the conditions of the agreement. If "no" then you can't, even if you have a syndication agreement. If "verify", then it may be available to syndicate, but there are extra restrictions or additional payment requirements, and you should contact the FT to find out what these are.
The URL of the content in the API.
The title of the content. For articles this is the main headline.