---
title: "Validate and verify external cloud credentials for driver"
method: POST
path: "/c2c/v4/drivers/{driverId}/verify"
tags: ["C2C"]
---

# Validate and verify external cloud credentials for driver

`POST /c2c/v4/drivers/{driverId}/verify`

External cloud credentials to be validated for structure and fields provided.
Verify external cloud authentication status.

## Path parameters

- `driverId` string, required — Identifier of the driver.

## Request body

- object — An external cloud-specific object that the driver will use to login to the external cloud. The structure of this object varies per driver implementation. It is recommended to have dedicated credentials for logging in to the external cloud in order not to violate possible concurrent users policies of the external cloud. In case of the HERE Tracking loopback driver, the maximum allowed concurrent user account tokens is 3 per account, therefore it is recommended to create a separate HERE account and grant it the required privilege to update the connector's project, and use that account in externalCloudInfo.

## Response `200`

Successful

## Other responses

- `400` — Bad request The request object is in an incorrect format or has values that are invalid or out of range. If available, further error details are provided in the response body.
- `401` — Unauthorized The request did not provide correct authentication details
- `404` — Not Found The specified resource was not found
- `501` — Not Implemented This feature is not yet available.

---

[API](https://skmtc.net/here/apis/tracking.md) · [All operations](https://skmtc.net/here/apis/tracking/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/here/tracking/revisions/efa162f7023c/schema)