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

# Create deal



## OpenAPI

````yaml /api/openapi.yaml post /crm/deals/
openapi: 3.0.3
info:
  title: Earth Care Network API
  version: v1
  description: >
    REST API for the Earth Care Network platform — directory, CRM, context,
    metering/credits, and the prospecting engine.


    This is a **curated** reference covering the headline endpoints with
    accurate paths, methods, auth, and representative request/response bodies.
    ECN's API is largely function-based (DRF `@api_view`/`APIView` without
    serializers), so the raw drf-spectacular dump is sparse today; as the v2
    refactor migrates views to serializer-backed generics, this file is
    superseded by the generated schema (`manage.py spectacular --settings
    ecn.settings_docs`). See https://docs.earthcare.network for guides and the
    MCP surface.
servers:
  - url: https://earthcare.network/api/v1
    description: Production
  - url: https://test.earthcare.network/api/v1
    description: Test
  - url: http://localhost:8000/api/v1
    description: Local
security:
  - TokenAuth: []
tags:
  - name: Auth
    description: Authentication and the current user.
  - name: Directory
    description: The public directory of regenerative businesses.
  - name: Context
    description: AI-ready Context Packs.
  - name: CRM
    description: Contacts, deals, and tasks.
  - name: AI
    description: Metered AI execution through the gateway.
  - name: Credits
    description: Wallet, rate cards, and the usage ledger.
  - name: Prospecting
    description: Go-to-market profiles and lead discovery with buying signals.
  - name: MCP
    description: MCP API key management.
  - name: Automation
    description: Workflow automation.
paths:
  /crm/deals/:
    post:
      tags:
        - CRM
      summary: Create deal
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - organization_id
                - title
              properties:
                organization_id:
                  type: string
                  format: uuid
                title:
                  type: string
                stage:
                  type: string
                  enum:
                    - lead
                    - qualified
                    - proposal
                    - won
                    - lost
                value:
                  type: number
      responses:
        '201':
          description: Created
components:
  securitySchemes:
    TokenAuth:
      type: apiKey
      in: header
      name: Authorization
      description: 'DRF user token. Format: `Token <token>`'

````