> ## Documentation Index
> Fetch the complete documentation index at: https://docs.predexon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Remove Partner Fee

> Remove your partner markup fee

Idempotent - calling it when no partner fee is set returns the current (default) policy.


## OpenAPI

````yaml DELETE /api/fees/policy
openapi: 3.1.0
info:
  title: Predexon Trading API
  description: Unified trading API for prediction markets
  version: 1.0.0
servers:
  - url: https://trade.predexon.com
security:
  - ApiKeyAuth: []
paths:
  /api/fees/policy:
    delete:
      tags:
        - Fees
      summary: Remove Partner Fee
      description: >-
        Remove your partner markup fee. The platform fee remains active.
        Idempotent — returns the current state even if no partner fee was set.
      operationId: remove_partner_fee
      parameters:
        - name: venue
          in: query
          required: true
          schema:
            type: string
            enum:
              - polymarket
          description: Venue to clear the partner fee for.
      responses:
        '200':
          description: Partner fee removed (or already absent)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FeePolicy'
              example:
                venue: polymarket
                enabled: true
                platformFeeBps: 0
                partnerFeeBps: 0
                partnerTreasuryAddress: null
                totalFeeBps: 0
        '400':
          description: Missing or invalid venue
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '401':
          description: API key required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '409':
          description: Concurrent modification — retry the request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
components:
  schemas:
    FeePolicy:
      type: object
      properties:
        enabled:
          type: boolean
          description: Whether fees are active
        platformFeeBps:
          type: number
          description: Platform fee in basis points
        partnerFeeBps:
          type: number
          description: Partner markup fee in basis points (0 if not configured)
        partnerTreasuryAddress:
          type: string
          nullable: true
          description: EVM address receiving partner fee revenue
        totalFeeBps:
          type: number
          description: 'Combined fee: platformFeeBps + partnerFeeBps'
    ApiError:
      type: object
      description: >-
        Unified error envelope returned by every endpoint on any 4xx or 5xx
        response. The `error` field is a stable snake_case code partners can
        branch on; `message` is the human-readable explanation (free-form, may
        change); `requestId` is the request correlation id (also returned in the
        `x-request-id` response header) — quote it when contacting support.
      required:
        - error
        - message
        - requestId
      properties:
        error:
          type: string
          description: >-
            Stable machine-readable code. See [Error
            codes](/trading-api/error-codes) for the full list. Snake_case,
            never renamed once shipped.
          example: insufficient_balance
        message:
          type: string
          description: >-
            Human-readable explanation. Free-form text that may include
            specifics (amounts, IDs, hints); do not parse — branch on `error`
            instead.
          example: 'Insufficient balance: need 50.000000, have 12.500000'
        requestId:
          type: string
          format: uuid
          description: >-
            Request correlation id. Quote this when filing a support ticket.
            Also returned in the `x-request-id` response header on every
            response (success or failure).
          example: a1b2c3d4-e5f6-7890-abcd-ef1234567890
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````