The Puree Developer API: Pull Your Catering Data Into Your Own Tools

Your data belongs to you, and you can reach it from your own tools. Puree’s Developer API lets you pull your account’s orders, customers, menu and more into whatever you like (a mailing-list sync, a menu feed for another website, a reporting dashboard, tomorrow’s deliveries in your routing app, docket PDFs from your own scripts) and, where the account owner allows it, keep Puree up to date from your other systems. It returns clean JSON, it’s scoped to a single account, and getting started takes about two minutes.

What It Covers

The account owner gives access area by area, to look things up or to change them as well.

Available now:

• Orders, to look up, with the notes on each one. With write access, add a note to a quote, set its chef and driver instructions, or attach and remove documents (attaching shows a document to the customer straight away). Quotes themselves are still created, priced and accepted in Puree.
• Customers, to look up and change: your customers, their contacts and addresses. Import a customer list from your CRM and keep it in sync.
• Items and categories and Packages, to look up and change: your menu, pricing, dietary and allergen codes, photos (JPEG, PNG, WebP or iPhone HEIC, up to 5 MiB), package descriptions, the supplier each item comes from, and what each package contains.
• Staff, to look up and change: your staff roles and rates, and the people who work your events. No pay information.
• Who works each shift, to look up and change: put your staff on a quote’s shifts, or take them off. Not for accounts that roster through Deputy.
• Delivery run sheet, to look up and change: each day’s deliveries and collections in run order, with addresses and contacts. Plan runs, departure times and drivers from your routing tool.
• Supplier deliveries and collections, to look up and change: how goods from each outside supplier arrive and go back for a quote. Nothing is ever emailed to the supplier from here.
• Dockets, to look up: the chef, driver, equipment and beverage dockets, event brief, consolidated docket and standard quote, and a day’s delivery run sheet, as the same PDFs Puree prints.
• Commentary and email templates, to look up and change: the reusable wording for quote sections and emails. Terms and conditions stay in Puree.
• Tasks, to look up and change: follow-ups for customers, quotes and enquiries, with due dates and reminders.
• Enquiries and opportunities (with their tags and notes), and tags, to look up and change.
• The menu headings, presentation styles and suppliers your items and packages refer to, and the venue types your quotes can carry.
• Newsletter groups and who is in them. Putting someone in a group never subscribes them.
• Recipes and ingredients, for accounts that use recipes.

Writes are sent as JSON, and a customer’s own id (external_id) is unique within the account, so an import can be re-run safely. Nothing is ever deleted outright: the only removals are taking a contact out of a newsletter group, taking a person off a shift, and unlinking a document from a quote, and the document stays in your library. Everything else is made inactive, completed or retired instead, so nothing your quotes depend on disappears. The The Developer API help page lists every area in full.

Mint a Token, Make a Request

Once access is enabled, head to Settings → API and AI access and create a personal access token. The account owner decides who can do this and what each person can read or change; see API and AI Access: Decide Who Can Connect AI to Your Puree Account. Then every request is just an Authorization header away:

curl https://puree.app/api/public/v1/customers \
  -H "Authorization: Bearer puree_at_your_token_here"

List endpoints are paginated and support a search parameter for fuzzy matching, so you can pull exactly the records you’re after. Each token is rate-limited to 60 requests per minute, which is plenty for syncs and exports.

Interactive Docs, Not Just a PDF

Every endpoint, parameter and response field is laid out in the API reference, with example responses, so you can see the exact shape of the data before you write a line of code. Try calls from your own tools, with a token you’ve created.

Open the API reference →

Getting Started

Just want to connect an AI assistant such as Claude, ChatGPT or Grok? You don’t need a token for that any more: add the Puree connector to your AI app and click Sign in to Puree. Connecting with an AI Agent shows you how.

For the full walkthrough — base URL, authentication, searching and paging, rate limits and error handling — see our The Developer API help page.

Want access enabled, or have feedback on which endpoints we should add next? Reach out to us at email@puree.app.