# The organization cannot take that reseller role

> Canonical HTML: https://screenrig.ai/problems/reseller-conflict

HTTP 409 · `reseller_conflict`

## What it means

The API answers with HTTP 409 Conflict and an `application/problem+json` document when the condition is The organization cannot take that reseller role. The document's `type` member is `https://screenrig.ai/problems/reseller-conflict`, the address of this page, and its `code` member is `reseller_conflict`.

## What to do

A reseller cannot be a customer of a reseller, an organization has at most one reseller, and staff and promo organizations take no part. The detail names the reason.

## Should you retry?

The `retryable` member appears only on HTTP 5xx problems, so this one has none. Follow the steps under What to do before sending the request again.

## Example response

Most routes answer with the error in the first entry of `errors`, and the document members `instance` and `request_id` beside it. The `type`, `code`, `title` and `status` of this problem type are fixed; `detail` varies per request, and `hint` is the registry default unless the handler sets a more specific one.

~~~http
HTTP/1.1 409 Conflict
Content-Type: application/problem+json

{
  "errors": [
    {
      "status": 409,
      "code": "reseller_conflict",
      "type": "https://screenrig.ai/problems/reseller-conflict",
      "title": "The organization cannot take that reseller role",
      "detail": "What went wrong in this request.",
      "hint": "A reseller cannot be a customer of a reseller, an organization has at most one reseller, and staff and promo organizations take no part. The detail names the reason."
    }
  ],
  "instance": "INSTANCE",
  "request_id": "REQUEST_ID",
  "server_time": "2026-01-01T00:00:00Z"
}
~~~

## In the API contract

The OpenAPI contract describes this problem in these words:

> The reseller starts at 2000 basis points of list price (20%) effective now and is pending review, boarding up to 10 current customers (customer_limit) until screenRIG reviews it. The organization must be live, not already a reseller, not a customer of a reseller and not on the staff or promo plan (409 reseller_conflict, the detail names the reason).

> Appends organization.created and reseller.customer_started to the organization audit. A reseller awaiting review (review_state pending) boards up to customer_limit current customers; past it the answer is 409 reseller_conflict.

## Operations that name this problem

These operations name this problem in the API reference:

- [Enroll Reseller](https://screenrig.ai/docs/api/dashboard#op-enrollReseller) — `POST /api/resellers`
- [Create Dashboard Reseller Customer](https://screenrig.ai/docs/api/dashboard#op-createDashboardResellerCustomer) — `POST /api/resellers/{reseller_id}/customers`

## Player action

This problem defines no Player action class. It belongs to a project, pairing or account flow that an agent or the dashboard drives.

## Reference

| Field | Value |
| --- | --- |
| Code | `reseller_conflict` |
| HTTP status | `409 Conflict` |
| Type | `https://screenrig.ai/problems/reseller-conflict` |
| Player action | `none` |

- [All problem types](https://screenrig.ai/problems)
- [API reference](https://screenrig.ai/docs/api#problems)
- [Problem registry YAML](https://screenrig.ai/docs/api/problems.yaml)