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

# Unlink Security

> Remove the linkage between a security and the partner's identifier.

### Request Body

- `security_guid` (string, required): GUID of the security to unlink.
    

### Response

- `status`: Operation status.



## OpenAPI

````yaml post /takeprofit.partner.external.security.v1.LinkApi.UnlinkSecurity
openapi: 3.0.0
info:
  title: TakeProfit Partner API
  description: TakeProfit Partner API documentation
  version: 0.1-beta
servers:
  - url: https://api.dev.tpinf.in
    description: Development environment
  - url: https://api.takeprofit.com
    description: '''Production environment'''
security: []
tags:
  - name: Partner API
  - name: Credentials
    description: >-
      The Credentials API allows partners to authenticate and obtain access
      tokens required for accessing other secured endpoints. This documentation
      provides details on how to use the authentication endpoints, including
      request and response formats.


      ## Overview


      The Authentication API provides two primary endpoints:


      1. **Create Token**: Authenticates a partner using their API key and
      returns an access token and a refresh token.
          
      2. **Refresh Token**: Generates a new access token using a valid refresh
      token.
  - name: Link
    description: >-
      The Link API allows partners to manage the linkage between their own
      securities and the securities provided by TakeProfit. This includes
      creating, retrieving, and deleting links between securities.
  - name: Reference API
    description: Set of APIs to get reference info such as exchanges, securities.
  - name: Marketdata API
    description: Set of APIs to get marketdata such as historical candles
  - name: Widgets
    description: |-
      Describe how to use TakeProfit Backend API from Widgets.

      Each request to API must has 'accesstoken' header with valid JWT-token.

      Describe here how to obtain JWT for widget.
paths:
  /takeprofit.partner.external.security.v1.LinkApi.UnlinkSecurity:
    post:
      tags:
        - Link
      summary: Unlink Security
      description: |-
        Remove the linkage between a security and the partner's identifier.

        ### Request Body

        - `security_guid` (string, required): GUID of the security to unlink.
            

        ### Response

        - `status`: Operation status.
      parameters:
        - name: accesstoken
          in: header
          schema:
            type: string
          description: JWT access token
          example: YOUR_ACCESS_TOKEN_HERE
      requestBody:
        content:
          application/json:
            schema:
              type: object
              example:
                security_guid: 6ef11658-5a1c-4baf-9387-d977dcca6129
      responses:
        '200':
          description: OK
          headers:
            content-type:
              schema:
                type: string
                example: application/json
            grpc-accept-encoding:
              schema:
                type: string
                example: identity,deflate,gzip
            grpc-encoding:
              schema:
                type: string
                example: identity
            date:
              schema:
                type: string
                example: Mon, 11 Nov 2024 09:56:21 GMT
            x-envoy-upstream-service-time:
              schema:
                type: integer
                example: '62'
            access-control-expose-headers:
              schema:
                type: string
                example: grpc-status, grpc-message, x-grpc-details, my-test
            my-little-header:
              schema:
                type: string
                example: my-test
            access-control-allow-origin:
              schema:
                type: string
                example: '*'
            grpc-status:
              schema:
                type: integer
                example: '0'
            grpc-message:
              schema:
                type: string
                example: OK
            content-length:
              schema:
                type: integer
                example: '97'
            server:
              schema:
                type: string
                example: envoy
          content:
            application/json:
              schema:
                type: object
              example:
                status:
                  code: 0
                  message: Security unlinked successfully.
                  details: []

````