Versioning

All requests to the API must provide an Accept header containing the version your application expects to handle the request.

Accept: application/vnd.gathercontent.v0.5+json

Be sure to provide the version of the API on every request – each example contains a version header for you.

What is the latest version of the API?

The current version is v0.5.

Why is the API not v1.0

Prior to the launch of our API, we provided a Plugins API which is still used for integrations with systems such as WordPress. We still maintain the Plugins API, however active development stopped at v0.4. Our integration plugins are currently being updated to use the latest version of our API.

Furthermore, we have also defined a backlog of functionality which constitutes v1.0 officially, so we opted to launch as v0.5.

Is the API ready for production?

Absolutely. In fact, we use the API within the application.

Any changes introduced to the interface will require a version bump in order to be adopted. We will never introduce breaking changes to any supported version of the API.

Which versions are currently supported?

v0.5

When will a version become unsupported?

We have no plans to drop support for any version of our API in the near future, however when we do – we will communicate a timeframe with all our customers still making requests with the version being dropped. We care deeply about our customers and will never intentionally cause any integrations to break.

Struggling to find what you need? Send a Message

Great, welcome aboard!

That’s it! You’re signed up to our mailing list and can expect content strategy goodness in your inbox soon.