# API Settings

You can enable or disable API from here and have other settings which will reflect on your API and hence on the mobile app.

### General API Settings

<figure><img src="/files/PTniKSOrk27TMqqplKCj" alt=""><figcaption></figcaption></figure>

You may turn on or off APIs here.

**API:** The admin user can restrict mobile app login. This means if the admin disables this API, the mobile app will not work.

**Google Location API**: You must provide an API key in the Driver Maps section in order to enable the Google Location API option. By turning on this feature, the user will be able to receive address recommendations from Google Maps when creating a new booking.

**Anyone can register:** The admin can directly control new registrations from the frontend or website. By enabling this option, the admin allows new registrations.

**Driver Review System**: By enabling the review feature, the admin can view newly submitted reviews posted by customers from the frontend.

<figure><img src="/files/t5vVgHmrWAcGjgwW6ueQ" alt=""><figcaption><p>Reviews</p></figcaption></figure>

**Region Availability:** You can type the name of your region here.

**Maximum Time a Trip can Go(in Days):** Admin can choose the maximum number of days for a trip here.

**Future booking timing (in days):** You can specify how many days in advance you can reserve a vehicle in the future.

**Cancel timing (in days):** Here, you may indicate how many days before your trip you can cancel.

### Firebase Settings

Steps to store firebase Database URL which is used in Android APP and to track Drivers in Admin panel

1. Sign in to Firebase Console and generate new private key of your firebase project which you will used for Fleet manager.
2. Rename your downloaded file to **firebase\_credentials.json**
3. Replace your file at **PROJECT\_FOLDER/framework/storage/firebase/** location
4. Then store your firebase Database URL here.

#### Refere below image to get your firebase private key.

![firebase-console](/files/-Mjs7Ml7vRZm2p09mbo9)

Admin user can upload the file under the Firebase settings.

<figure><img src="/files/4xQGIcHqsWAuIDHtwBqA" alt=""><figcaption><p>Firebase settings</p></figcaption></figure>

### Driver Maps

**Web API Key for google maps** <i class="fa-info-circle">:info-circle:</i>

To track driver positions, respond to suggestions in bookings, and determine total mileage, input the API key.&#x20;

{% hint style="danger" %}
**To view the Driver Maps module in the system, the following information must be provided.**\
\
The admin must upload the Firebase JSON file under the API Settings module.

For Driver Maps, the admin must set the Google Maps Web API key and the Firebase API key in the API Settings.

The logged-in user must be granted permission or access to Driver Maps from User Access Management under the Settings module.<br>
{% endhint %}

<figure><img src="/files/kXMfJozb2fKJZkNHIvZD" alt=""><figcaption></figcaption></figure>

**Firebase Setting Web API Key** <i class="fa-info-circle">:info-circle:</i>

Firebase is used to connect the system with the Android app and enable real-time features like driver tracking, authentication, and data sync.

<figure><img src="/files/StfiGvecmlRkD2j0ifi9" alt=""><figcaption></figcaption></figure>

**Info (ⓘ)**\
The Firebase Web API Key connects the Fleet web application with Firebase services such as authentication and real-time database, enabling seamless communication between the admin panel and mobile app.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://fleetdocs.hyvikk.space/explore-features/settings/api-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.