> ## Documentation Index > Fetch the complete documentation index at: https://developer.plugsurfing.com/llms.txt > Use this file to discover all available pages before exploring further. # Start a remote session > Starts a remote charging session with the given charging key on the given connector. If a user has `CREDIT_CARD` payment method, and 3DS challenge mode is set to `CHALLENGE`, then `threeDSClientSecret` might be present instead of `sessionId`, which your frontend needs to prompt the user to sign. After the user successfully signs the challenge, do a second start request! ## OpenAPI ````yaml reference/openapi.json POST /emp/v1/sessions/start openapi: 3.1.0 info: title: Drive API version: 1.0.0 description: >- The Drive API provides comprehensive access to Plugsurfing's charging infrastructure network. It enables you to manage users, charging keys, search for charging locations, handle payments, and control charging sessions. servers: - url: https://{environment}.plugsurfing.com variables: environment: enum: - drive-api-stage default: drive-api-stage description: >- API environment - use drive-api-stage for testing and drive-api for production security: [] tags: - name: Geosearch description: >- Search and retrieve detailed information about charging locations and stations - name: Users description: >- Manage user accounts including creation, retrieval, updates, and deletion. Handles user-specific data and preferences. - name: Charging Keys description: >- Manage physical and virtual charging keys including creation, activation, updates, and status management. Essential for user access to charging stations. - name: Sessions description: >- Access and manage charging session data including history, status, and detailed session information - name: Remote Charging description: >- Control charging sessions remotely including starting and stopping sessions, and monitoring session status - name: Payment Options description: >- Manage payment methods and handle transaction processing for charging services - name: User Groups description: Manage user group memberships - name: Vouchers description: Redeem vouchers - name: Charging Key Orders description: Handle the ordering and fulfillment process for physical charging keys - name: EMP Charging Keys description: E-Mobility Provider specific endpoints for managing charging keys - name: EMP Geosearch description: E-Mobility Provider specific endpoints for location search and information - name: EMP Orders description: E-Mobility Provider specific endpoints for managing orders - name: EMP Sessions description: E-Mobility Provider specific endpoints for managing charging sessions - name: EMP Fleets description: E-Mobility Provider specific endpoints for managing fleets paths: /emp/v1/sessions/start: post: tags: - EMP Sessions summary: Start a remote session description: >- Starts a remote charging session with the given charging key on the given connector. If a user has `CREDIT_CARD` payment method, and 3DS challenge mode is set to `CHALLENGE`, then `threeDSClientSecret` might be present instead of `sessionId`, which your frontend needs to prompt the user to sign. After the user successfully signs the challenge, do a second start request! operationId: startRemoteSessionEmp requestBody: content: application/json: schema: $ref: '#/components/schemas/EmpSessionStartRequest' example: connectorId: >- aHeS4zN1UjzJf/HVDH66SbaItXqHvfLxexulktxTqJavgcbozuV9KJGqNYjmaQPwTb4Ck9wTZcWeEdfeco1srw== keyIdentifier: BnZd3qp87z responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/SessionStartResponse' example: sessionId: AAdmD55q8Vz threeDSClientSecret: pi_3MtwBwLkdIwHu8ix28v3tqPa_secret_YrKJUkribcBjcG7HVhfZluoGH '400': description: The provided query parameters, route parameters or body is invalid. content: application/json: schema: $ref: '#/components/schemas/InvalidRequestErrorResponse' example: message: Invalid request payload details: - field X is required '403': description: >- Forbidden. The charging key is not allowed to charge, or the connector won't allow remote charging. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: message: Resource not found '404': description: Charging key or connector is not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: message: Resource not found '500': description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: message: Resource not found security: - ApiKeyAuth: [] components: schemas: EmpSessionStartRequest: required: - connectorId - keyIdentifier type: object properties: connectorId: type: string example: >- aHeS4zN1UjzJf/HVDH66SbaItXqHvfLxexulktxTqJavgcbozuV9KJGqNYjmaQPwTb4Ck9wTZcWeEdfeco1srw== description: Connector identifier to start charging on. keyIdentifier: type: string example: BnZd3qp87z description: Charging key identifier used for authorization. description: EMP session start request identifying connector and charging key. SessionStartResponse: type: object description: >- SessionId will always be present, unless CREDIT_CARD reservation for a user is required during authentication, then either sessionId or threeDSClientSecret will be present. properties: sessionId: type: string description: This session id should be stored and used in other endpoints. example: AAdmD55q8Vz threeDSClientSecret: type: string description: >- Will only be available for users with CREDIT_CARD payment methods, when CHALLENGE mode has been enabled for 3DS challenges. The 3DS client secret can be used to complete a payment from your frontend. If not present, no user authentication is required to start the session. example: pi_3MtwBwLkdIwHu8ix28v3tqPa_secret_YrKJUkribcBjcG7HVhfZluoGH InvalidRequestErrorResponse: title: InvalidRequestErrorResponse type: object required: - message - fields properties: message: type: string fields: type: array items: title: InvalidField type: object required: - name - message - rejectedValue properties: name: type: string message: type: string example: UserId is not correct rejectedValue: type: string ErrorResponse: title: ErrorResponse type: object properties: message: type: string securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key description: API key for authentication ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.