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

# Delete API Keys

> This endpoint allows you to delete a specific API integration for a company using the provided API key ID.

### Request Body

This request does not require a request body.

### Response

- `message` (string): A message indicating the result of the operation.
    
- `status` (integer): A status code indicating the outcome of the request.
    
- `data` (object, optional): Additional data related to the operation, if available. In the provided example, it includes a variable field.
    

#### Example Response

``` json
{
    "message": "Success",
    "status": 200
}

 ```



## OpenAPI

````yaml delete /v1/company/api-integrations/{api-key-id}
openapi: 3.0.0
info:
  title: Pauls Job Public Endpoints
  description: >-
    #### **Description:**


    This API provides a comprehensive suite of endpoints for managing user
    authentication, session control, and other key functionalities within the
    application for Pauls Job. The endpoints are designed to ensure secure and
    efficient communication between clients and the server, offering robust
    access control mechanisms through token-based authentication.


    #### **Key Features:**


    - **Authentication:** Allows users to securely log in using their
    credentials and receive a token for accessing protected resources.
        
    - **Session Management:** Provides a logout mechanism to securely end user
    sessions and invalidate tokens.
        
    - **Error Handling:** Clear and descriptive error messages ensure that
    issues such as invalid credentials, expired tokens, or missing parameters
    are easily identifiable.
        

    This API is built with a focus on security and ease of use, making it
    essential for integrating user authentication and session management into
    applications while maintaining a high standard of data protection.
  version: 1.0.0
servers:
  - url: https://api.hyrd.de
security: []
tags:
  - name: Users
    description: >-
      #### **Description:**


      The folder contains the foundational information and essential API
      endpoints for starting with the authentication and session management of
      the application. This includes the critical login and logout
      functionalities, which are necessary for users to authenticate and manage
      their sessions securely.


      #### **APIs Included:**


      1. **Login API**: Allows users to log in by providing their credentials
      and receive an authentication token.
          
      2. **Logout API**: Enables users to log out by invalidating the token and
      ending their session.
          

      These endpoints are designed to facilitate secure access control and
      session handling, making them an essential starting point for any
      interaction with the platform's protected resources.
  - name: General
  - name: Company
  - name: Company > Candidate
  - name: Company > Api Integrations
paths:
  /v1/company/api-integrations/{api-key-id}:
    delete:
      tags:
        - Company > Api Integrations
      summary: Delete API Keys
      description: >-
        This endpoint allows you to delete a specific API integration for a
        company using the provided API key ID.


        ### Request Body


        This request does not require a request body.


        ### Response


        - `message` (string): A message indicating the result of the operation.
            
        - `status` (integer): A status code indicating the outcome of the
        request.
            
        - `data` (object, optional): Additional data related to the operation,
        if available. In the provided example, it includes a variable field.
            

        #### Example Response


        ``` json

        {
            "message": "Success",
            "status": 200
        }

         ```
      parameters:
        - name: api-key-id
          in: path
          schema:
            type: integer
          required: true
          example: '2'
      responses:
        '200':
          description: OK
          headers:
            Content-Type:
              schema:
                type: string
                example: application/json
          content:
            application/json:
              schema:
                type: object
              examples:
                example-0:
                  summary: Success
                  value:
                    message: Success
                    status: 200
                example-1:
                  summary: Api Key not found
                  value:
                    message: Api Key könnte nicht gefunden werden
                    status: 404
                    data:
                      variable: Api Key

````