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

# Party Relationship

> This API endpoint allows you to establish a relationship between two parties. The request body should  specify the party ID and the desired relationship type.




## OpenAPI

````yaml POST /omni-omni/v1/parties/{email}/relationships
openapi: 3.0.1
info:
  contact:
    email: developers@ecrop.com
    name: ecrop OmniOmni API Support
    url: https://ecrop.de/contact/
  description: >
    # Preparation Guide

    Welcome to the comprehensive API Documentation. This document provides a
    detailed list of available APIs and methods. Before beginning your
    integration, it’s recommended to review the following essential documents:


    - **API Service Guide (Essential, Pro):** Designed for non-technical users,
    this guide helps in selecting the best API package based on business needs.
    Review it
    [here](https://youki.atlassian.net/wiki/spaces/mar/pages/534183949/API+Service+Guide).


    - **Integration Handbook:** Targeted at developers, this handbook includes
    crucial details such as endpoint URLs, authentication methods,
    request/response formats, and error handling. It is essential for successful
    integration. Access the handbooks here:

      - [🌳 Pro Package Integration Handbook]

      - [🌱 Essential Package Integration Handbook]

    Familiarizing yourself with these documents will ensure a smoother
    integration process.
  license:
    name: ecrop OmniOmni
    url: https://developers.ecrop.de/api-license/
  termsOfService: https://developers.ecrop.de/terms-of-use/
  title: OmniOmni API Catalogue
  version: 1.0.0
  x-logo:
    backgroundColor: '#DDDDDD'
    url: >-
      https://static.wixstatic.com/media/fd3e8b_a57864adb1084dea94c9fab462a8f52c~mv2.png/v1/crop/x_0,y_131,w_1253,h_295/fill/w_233,h_55,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/fd3e8b_a57864adb1084dea94c9fab462a8f52c~mv2.png
servers:
  - description: Default
    url: https://backend.sandbox.ecrop.de/ecrop-command
security:
  - Bearer Authentication: []
tags:
  - name: Auth
    description: Endpoints for OmniOmni security
  - name: Offers
    description: >
      Opportunities establishment to transfer securities between parties,
      including User interactions expressing interest in an offer
  - name: Assets
    description: >-
      Financial or non-financial instruments that can be transferred between two
      parties
  - name: Investments
    description: Asset displacement among 2 parties under offer conditions
  - name: Transfers
    description: Asset displacement among 2 parties
  - name: Documents
    description: Any document that is generated for any user action
  - name: Parties
    description: >
      A representative of individuals or any registered company, organization,
      etc...
paths:
  /omni-omni/v1/parties/{email}/relationships:
    post:
      tags:
        - Parties
      summary: 🌱 Create a new relationship between two parties
      description: >
        This API endpoint allows you to establish a relationship between two
        parties. The request body should  specify the party ID and the desired
        relationship type.
      operationId: addPartyRelationship
      parameters:
        - in: path
          name: email
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/OmniOmniPartyRelationshipDto'
        required: true
      responses:
        '201':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OmniOmniPartyRelationshipDto'
          description: Party relationship is created
        '404':
          description: Party's email not found
components:
  schemas:
    OmniOmniPartyRelationshipDto:
      type: object
      properties:
        id:
          type: integer
          format: int64
          readOnly: true
        partyEmail:
          type: string
        relationshipDirection:
          type: string
          enum:
            - MEMBER
            - PARENT
        relationshipType:
          type: string
          enum:
            - EXECUTIVE
            - SUPERVISORY
            - GENERAL_MEETING
            - EMPLOYEE
            - SHARE_HOLDER
            - CONTROLLING_PERSON
            - DIRECTOR
            - CEO
            - BOARD_CHAIRMAN
            - BOARD_MEMBER
            - SPOUSE
            - HERITAGE
      required:
        - partyEmail
        - relationshipDirection
        - relationshipType
  securitySchemes:
    Bearer Authentication:
      bearerFormat: JWT
      scheme: bearer
      type: http

````