---
title: "Business Offer Discount Model"
description: "This guide describes the business-scoped Offer resource under /business/{business_id}/offers."
canonical: https://docs.ordering.co/api-reference/guides/offers-model/
---

# Business Offer Discount Model

This guide describes the business-scoped `Offer` resource under `/business/{business_id}/offers`. It is distinct from the project-wide advanced-offer context documented in [Advanced offers model](https://docs.ordering.co/api-reference/guides/offers-model-1/).

## Business-scoped operations

| Action | Method          | Resource                                    |
| ------ | --------------- | ------------------------------------------- |
| List   | `GET`           | `/business/{business_id}/offers`            |
| Find   | `GET`           | `/business/{business_id}/offers/{offer_id}` |
| Create | `POST`          | `/business/{business_id}/offers`            |
| Update | `PUT` or `POST` | `/business/{business_id}/offers/{offer_id}` |
| Delete | `DELETE`        | `/business/{business_id}/offers/{offer_id}` |

Do not rely on anonymous access for numeric offer lookups; they may require an administrator or business-manager account. Coupon lookups can also depend on offer type, remaining uses, and dates.

Representative fields include `id`, `business_id`, `name`, `type`, `minimum`, `rate_type`, `rate`, `start`, `end`, `coupon`, `limit`, and `enabled`. Historical examples use `type=1` for an automatically applied offer, `type=2` for a coupon, `rate_type=1` for a percentage, and `rate_type=2` for a fixed amount. Verify accepted values for the operation before relying on them.

Use [Business offer relation expansion](https://docs.ordering.co/api-reference/guides/offers-special-request/) when you need the business relation.