Versioning

Hi! There's a new version available (api2), recommended for all new and future development.

We plan to continue to support the legacy version of the API well into 2017 (and later if you let us know), but we do recommend all developers migrate to the new api2 format as your development cycle allows. We strongly recommend that all new recipe and grocery API developers begin with https://api2.bigoven.com

API OVERVIEW

AUTHENTICATION

Authentication Process

API PROTOCOL

API DATA

DATA MANAGEMENT

BRANDING, LEGAL & FINANCIAL

The BigOven API strives to provide a consistent consumer experience. To this end, a versioning scheme has been designed to address future changes in the API.

Current Version

For the current version of the API, hereafter the “working version”, all request URLs will be of the form

https://api.bigoven.com/{query}

By targeting the working version, the consumer understands that future API changes may cause an implementation to operate in a different manner than originally intended. It is the responsibility of the consumer to synchronize with API changes.

Targeting a Version

For developers unwilling to update an implementation in a consistent manner, a particular version of the API may be specified in each request. Requests of this type will take the form

https://api.bigoven.com/v{#}/{query}

where v{#} could be v1, v2, v3, etc.

However, we strongly recommend targeting the current version of the API at https://api.bigoven.com

Lifespan of a Version

While the consumer can expect a specific version of the API to be available for a considerable period of time, BigOven reserves the right to discontinue support for any historical version of the API with six (6) months of advance warning.

BigOven API