Noticed anything incorrect or missing? Please contact us to report this.
Connect to FT APIs
All your requests to any FT API should use the following base URL:
You must supply a valid API Key with each request. This should be done with an X-Api-Key request header:
Your API key identifies your application as a legitimate user of the FT API. It may only be shared in accordance with the terms of your license.
In particular, you must not include your API key in any app, Web site or script which is served to unlicensed users. For example, if you are building a browser-based app, the browser should only make requests to a service under your control, which would be responsible for authorizing the app, making FT API calls as necessary, and building an appropriate response.
Your API key may be throttled if it makes too many requests. To ensure your application continues to function, you should agree an appropriate traffic level with us beforehand, taking into account any opportunities you will have to cache data.
You can also supply an API key in a query parameter apiKey
If you use this method, you should make sure your client correctly supplies this parameter to all requests, including in response to redirects.
If you want specific guidance on how best to use the FT API in your application, please contact us
The second version of the FT's Content API provides access to information about FT articles, blog posts and FastFT posts. See API v2 Reference for futher details. A change feed provides a way to find new content as it is published.
We do not expect to make changes that break existing integrations, but you should make sure your code is flexible, for example able to cope with new fields being included in responses.
Search all items of content. This will return a list of content items. Some item properties are not available using this method. Full details can be retrieved using the Get method for a particular item of content.
Note: although the endpoint for this API contains “v1”, we are extending its life so it will continue to function after the other v1 endpoints (see below) are removed. You can continue using this API for existing and new projects.