Terms of service

You need an account to get an API key. Keep your password and your keys to yourself — anything done with your key counts as done by you. If a key leaks, revoke it from your dashboard; that takes effect at once.

One account per person or organisation. Do not create accounts to work around the rate limit.

Your account gets 500 requests a day across all of its keys, as described under rate limits. Stay within it, and cache what does not change rather than re-requesting it.

Do not:

• attempt to disrupt the service, or work around its limits or authentication;
• resell the API itself, or pass it off as your own service;
• systematically copy the index — paging through the endpoints to build your own database of it, walking the id space, or spreading that work across accounts, keys or addresses;
• use it for anything unlawful.

The last one is the line we care most about. This API is for looking up the recipes your users actually ask for. Cache those and let the cache expire — what is not allowed is accumulating the corpus until you have a copy of it. If you want the dataset in bulk, ask us at chris@pullpanda.io rather than taking it a page at a time; there is often a way to say yes.

The recipes belong to the people and sites that published them, not to us. We normalize them and link back. If you display a recipe you got from this API, credit its source and link to the url the response carries.

Nothing here grants you rights in a recipe beyond what its publisher allows. Bulk-republishing whole recipes as your own is not something this API can give you permission to do.

Publishers: to have your site removed, write to chris@pullpanda.io.

The service is provided as it is. Recipes are gathered automatically and normalized by software, and both can be wrong — an ingredient misparsed, a time missing, a dietary flag inferred rather than declared. Nutrition and dietary information in particular is not reliable enough to depend on for health or allergy decisions. Check against the source before you rely on anything.

We do not promise the API will be available, complete or uninterrupted, and we are not liable for losses arising from its use, so far as the law allows.

You can stop using the API at any time and ask us to delete your account — see privacy. We may suspend an account that breaks these terms, and will say why where we can.

These terms may change as the service does. Material changes will be posted here before they take effect, and keys will not be made required without notice — see authentication.