> ## 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.

# Auth

> This API endpoint is used to authenticate client and obtain access tokens. By providing the necessary credentials, typically in the request body, clients can initiate a sign-in process. Successful authentication will result in the issuance of an access token, which can be used for subsequent API calls.




## OpenAPI

````yaml POST /v1/auth/client-token
openapi: 3.0.1
info:
  contact:
    email: developers@ecrop.com
    name: ecrop OmniSafe API Support
    url: https://ecrop.de/contact/
  description: >
    # Preparation Guide

    Welcome to the OmniSafe API Documentation. This document provides a detailed
    list of available APIs and methods for managing wallets, tokens, and
    transfers. 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).  # Keep or adapt

    - **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] # Keep or adapt

      - [🌱 Essential Package Integration Handbook] # Keep or adapt

    Familiarizing yourself with these documents will ensure a smoother
    integration process.
  license:
    name: ecrop OmniSafe
    url: https://developers.ecrop.de/api-license/
  termsOfService: https://developers.ecrop.de/terms-of-use/
  title: OmniSafe 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://omnisafe.sandbox.ecrop.de/omni-safe
security:
  - Bearer Authentication: []
tags:
  - name: Wallets
    description: Endpoints for managing wallets
  - name: Tokens
    description: Endpoints for managing tokens
  - name: Transfers
    description: Endpoints for managing transfers
paths:
  /v1/auth/client-token:
    post:
      tags:
        - Auth
      summary: 🌱 Client Sign-In
      description: >
        This API endpoint is used to authenticate client and obtain access
        tokens. By providing the necessary credentials, typically in the request
        body, clients can initiate a sign-in process. Successful authentication
        will result in the issuance of an access token, which can be used for
        subsequent API calls.
      operationId: signInClient
      parameters:
        - in: header
          name: X-Signature-DateTime
          schema:
            type: string
        - in: header
          name: X-Signature
          schema:
            type: string
        - in: header
          name: X-Signature-DeviceId
          schema:
            type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ClientSignInRequest'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ClientSignInResponse'
          description: User signed in successfully
        '401':
          description: Invalid credentials
        '404':
          description: Client not found
      security: []
components:
  schemas:
    ClientSignInRequest:
      type: object
      properties:
        clientId:
          type: string
    ClientSignInResponse:
      type: object
      properties:
        accessToken:
          type: string
  securitySchemes:
    Bearer Authentication:
      type: http
      scheme: bearer
      bearerFormat: JWT

````