> ## Documentation Index > Fetch the complete documentation index at: https://api.leadey.ai/llms.txt > Use this file to discover all available pages before exploring further. # Mark an opportunity lost > Moves it to the pipeline's lost stage and fires `opportunity.lost`. Permissions are the same as in the app, resolved from the member your API key acts as. Without `opportunities.editAll` you can only change opportunities you own — an API key is not a way around the rules a person has. ## OpenAPI ````yaml /openapi.json post /opportunities/{id}/lose openapi: 3.1.0 info: title: Leadey API version: 1.4.0 description: >- The Leadey API gives you programmatic access to your workspace: leads, companies, contacts, campaigns, meetings, opportunities and calls, plus the reporting metrics behind the Cockpit. Every request is authenticated with an organization-scoped API key, and every response is JSON. Reads work with any key. Writes — creating leads, adding notes, logging calls, managing tasks — need a key with write access, and are attributed to the workspace member that key belongs to. See [Writing data](/guides/writing-data). servers: - url: https://backend.leadey.ai/v1 description: Production - url: http://localhost:3001/v1 description: Local development security: - bearerAuth: [] tags: - name: Account description: The organization behind the API key. - name: Leads description: People enrolled in your campaigns. - name: Notes description: >- Free-text notes on a lead. Notes appear in the lead's timeline and in the Cockpit. - name: Tasks description: Follow-ups and reminders, each assigned to a workspace member. - name: Campaigns description: Outreach sequences and their performance. - name: Companies description: Companies in your workspace. - name: Contacts description: The canonical person record behind your leads. - name: Meetings description: Bookings merged across Calendly, Leadey and connected calendars. - name: Opportunities description: Deals, their value, and the pipelines they sit in. - name: Pipelines description: Deal pipelines and the stages inside them. - name: Calls description: Dial history, recordings and transcripts. - name: Metrics description: >- Aggregated reporting — meetings booked, sit rate, dial activity and pipeline value. - name: Reference description: The vocabularies other endpoints return values from. paths: /opportunities/{id}/lose: post: tags: - Opportunities summary: Mark an opportunity lost description: >- Moves it to the pipeline's lost stage and fires `opportunity.lost`. Permissions are the same as in the app, resolved from the member your API key acts as. Without `opportunities.editAll` you can only change opportunities you own — an API key is not a way around the rules a person has. operationId: loseOpportunity parameters: - name: id in: path required: true schema: type: string requestBody: required: true content: application/json: schema: type: object properties: reason: type: string responses: '200': description: Success content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/Opportunity' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' components: schemas: Opportunity: type: object properties: id: type: string name: type: string value: type: string description: >- Decimal string with 2 places. A string, not a number, so no precision is lost in transit. example: '15000.50' currency: type: string example: GBP probability: type: integer description: >- Effective close probability: the deal's own override if set, otherwise its stage's default. example: 40 status: type: - string - 'null' enum: - open - won - lost - null description: Derived from the stage's type. pipelineId: type: string stageId: type: string stageLabel: type: - string - 'null' ownerId: type: - string - 'null' description: Resolve against `GET /users`. companyId: type: - string - 'null' contactId: type: - string - 'null' sourceLeadId: type: - string - 'null' description: The campaign lead this deal was converted from, if any. expectedCloseDate: type: - string - 'null' format: date closedAt: type: - string - 'null' format: date-time lostReason: type: - string - 'null' createdAt: type: string format: date-time updatedAt: type: string format: date-time required: - id - name - value - currency - status Error: type: object properties: error: type: object properties: message: type: string description: Human-readable error message. details: type: - object - array - string - 'null' description: Optional structured detail. required: - message responses: BadRequest: description: The request was malformed, or a required field was missing or invalid. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: One of email, phone or linkedinUrl is required details: null Unauthorized: description: The API key is missing, invalid, or revoked. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: Invalid or revoked API key. details: null Forbidden: description: >- The key is read-only, or the workspace is not currently allowed to write (payment method missing, trial expired, payment overdue, or subscription cancelled). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: >- This API key is read-only. Create a key with write access in Settings → API Keys. details: null NotFound: description: The resource does not exist or is not in your workspace. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: Lead not found details: null securitySchemes: bearerAuth: type: http scheme: bearer description: >- Your API key, created in the Leadey dashboard under Settings → API Keys. Send it as `Authorization: Bearer leadey_sk_live_…`. ````