API Changelog

This changelog describes changes that have been made to the DataSift API over time and includes dates for when API versions will be deprecated.

To keep up-to-date with platform and API changes please subscribe to the Announcements category on the community site. You can read more about versioning in our API Versioning and Deprecation Policy.

API Versions

Version Path Date Introduced Available Until
(default) /{endpoint} November 2011 1st March 2016
v1.0 /v1/{endpoint} November 2011 1st April 2016
v1.1 /v1.1/{endpoint} January 2014 1st May 2016
v1.2 /v1.2/{endpoint} September 2015 1st March 2017
v1.3 /v1.3/{endpoint} March 2016 --

Changelog

Version 1.3 - (March 2016)

  • /pylon/start - The endpoint now returns an id when you start a recording. This id should be used to reference the recording in subsequent API calls.
  • /pylon/stop - Requires the id of the recording you want to stop, rather than the hash as in API 1.2.
  • /pylon/analyze - Requires the id of the recording you want to analyze, rather than the hash as in API 1.2.
  • /pylon/get - To retrieve details of an individual recording you now provide an id rather than a hash.
  • /pylon/tags - Requires the id of the recording you want to list tag namespaces for, rather than the hash as in API 1.2.
  • /pylon/sample - Requires the id of the recording you want to retrieve samples for, rather than the hash as in API 1.2.
  • /pylon/update - A new endpoint that allows you to update the interaction filter definition for a recording.

Version 1.2 - (September 2015)

  • /push/create - Previously playback_id was supported as an alias for the historics_id parameter. It is no longer supported.
  • /pylon/get - Introduced paging to endpoint including current page details to the endpoint response.
  • Introduced 429 HTTP status code for all endpoints. This is returned when you hit your API rate limit.

Version 1.1 - (January 2014)

  • /push/get
    • Previously playback_id was supported as an alias for the historics_id parameter. It is no longer supported.
    • Introduced interaction_count field to response, indicating the number of interactions delivered.
  • /historics/get
    • Removed the volume_info field from the endpoint response structure.
    • Added the with_estimate field to the response when the optional id parameter is not provided.
    • Added delivery_count field to the overall response and each chunk, to show the number interactions delivered.