# Introduction

Get up and running with Stoovo's API. Explore our API Endpoints, Data Guides, and more.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Stoovo Data</strong></td><td></td><td></td><td><a href="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2FrplcmGVhhmmwqdGd71sh%2FAddress%20data.png?alt=media&amp;token=e8c0c11a-22e7-49c8-bba6-dd6ebd989c74">Address data.png</a></td><td><a href="/getting-started/location-data-and-insights">Location Data &amp; Insights</a></td></tr><tr><td><strong>Demo Endpoints</strong></td><td></td><td></td><td><a href="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2FpVIYRUVR8tSlB1sGB8Rq%2FApi%20overview.png?alt=media&amp;token=36e3ef66-5530-4989-9e44-fc601db61cf2">Api overview.png</a></td><td><a href="/getting-started/demo-enpoints">Demo Enpoints</a></td></tr></tbody></table>


# Location Data & Insights

Here are the articles in this section


# Schema

All the addresses are returned in standard GeoJSON feature object. Each address has its own feature objects with few additional fields.

**Response Object**:

| Parameter  | Type            | Descriptions                                                                                                                                       |
| ---------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| placeId    | string          | Stoovo generated Unique ID                                                                                                                         |
| type       | string          | Standard Geojson format type, it could be 'Feature'. You can read about it more [here](https://datatracker.ietf.org/doc/html/rfc7946#section-3.2). |
| geometry   | Geometry Object | Standard RC 7946 Geometry Object with type as Point. Read more [here](https://datatracker.ietf.org/doc/html/rfc7946#section-3.1).                  |
| properties | POI Object      | All the point of interest details are inside the properties.                                                                                       |

**POI Property Object:**\
Each POI Object encompasses intricate details such as entrances, parkings, delivery options, and other descriptors, with a payload offering variable instructions for each.

| Parameter      | Type                      | Descriptions                                                                                                                                                                                                                                            |
| -------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| buildingType   | String                    | Type of the building, one of apartment, house, office, store or other                                                                                                                                                                                   |
| address        | String                    | Standardized location's address                                                                                                                                                                                                                         |
| floors         | Number                    | Number of floors in the building.                                                                                                                                                                                                                       |
| apn            | String                    | A unique number assigned to a parcel of property by the local tax assessor's office to identify it for property tax purposes. This number is specific to the real estate industry and is used primarily for property identification and record-keeping. |
| openingHours   | Array                     | Array of 7 elements of text with opening hours for 7 days.                                                                                                                                                                                              |
| curbsidePickup | Boolean                   | True, if curb side pick up is available for this location.                                                                                                                                                                                              |
| building       | Building Object           | This gives information about the building                                                                                                                                                                                                               |
| delivery       | Delivery Object           | This gives more information catered for delivery. Such as dropoff Type and specific delivery instructions for that address.                                                                                                                             |
| boundaries     | Feature Collection Object | Generally shape of the poi interest address, it is coordinates describing the address.                                                                                                                                                                  |
| photos         | Array                     | Consists of array of pictures for that address.                                                                                                                                                                                                         |
| waypoints      | Array of Feature Objects  | This is different from features, waypoints are point objects inside the buildings such as elevators, stairs.                                                                                                                                            |
| entrances      | Feature Collection Object | Entrances of the poi of interest address. It also have subkind as Emergency door and handicap doors.                                                                                                                                                    |
| units          | Feature Collection Object | Each unit in the building, with floor and unit number as their properties.                                                                                                                                                                              |
| footpaths      | Feature Collection Object | Footpaths around the buildings                                                                                                                                                                                                                          |
| parking        | Feature Collection Object | Locations where visitors can park their vehicles.                                                                                                                                                                                                       |

**Building Object:**\
Building Object provides comprehensive details, including height, area, length and floor for a specified point of interest

| Parameter | Type   | Descriptions                      |
| --------- | ------ | --------------------------------- |
| height    | number | Height of the building            |
| area      | number | Area spread out of the building   |
| length    | number | Length of the building            |
| floor     | number | Number of floors in the building. |

**Feature Collection Object:**\
This object encompasses multiple points of interest, providing a comprehensive representation of various features within the system. These contains GeoJson Collection Feature Object with features as points objects. Feature collection object is array of features.

Feature Object Details:

This represents a feature object that is presented as an array within Feature Collection objects.

<table><thead><tr><th width="233">Parameter</th><th>Type</th><th>Descriptions</th></tr></thead><tbody><tr><td>type</td><td>string</td><td>Standard Geojson format type, it is point, polygon or line as string. You can read about it more <a href="https://datatracker.ietf.org/doc/html/rfc7946#section-3.1.2">here</a>.</td></tr><tr><td>geometry</td><td>Geojson Geometry</td><td>Array of coordinates for the point of that feature.</td></tr><tr><td>properties</td><td>Object</td><td>consists name and Stoovo generated id. ( floor and unit for units)</td></tr></tbody></table>

**Delivery Object:**

This specifies the delivery instructions and details on where to deliver.

| Parameter            | Type   | Descriptions                                                                        |
| -------------------- | ------ | ----------------------------------------------------------------------------------- |
| dropoffType          | string | One of mailbox, frontdoor, reception', mailroom, staff, backdoor, sideporch, garage |
| buildingInstructions | string | Instructions on delivery package                                                    |
| timeToDeliver        | string | Average delivery times on this location.                                            |

**Waypoint Object:**

It provides information and coordinates for a specific point inside the building. Generally helps in indoor navigation to that points. This is also feature collection object.

The following represents a feature object that is presented as an array within Feature Collection objects.

<table><thead><tr><th width="233">Parameter</th><th>Type</th><th>Descriptions</th></tr></thead><tbody><tr><td>type</td><td>string</td><td>Standard Geojson format type, it is point object. You can read about it more <a href="https://datatracker.ietf.org/doc/html/rfc7946#section-3.1.2">here</a>.</td></tr><tr><td>geometry</td><td>GeoJSON Point Object</td><td>Geojson Point Object.</td></tr><tr><td>properties</td><td>Waypoint Property Object</td><td>consists text (description of waypoint), id of the waypoint (id is Stoovo generated) and waypointKind.</td></tr></tbody></table>

Waypoint Property Object:

| Parameter | Type         | Descriptions      |
| --------- | ------------ | ----------------- |
| type      | waypointKind | Type of Waypoints |

Waypoints Kind Descriptions:

| Waypoints      | Descriptions                           |
| -------------- | -------------------------------------- |
| Elevator       | An elevator inside the building        |
| Deliverylocker | A Delivery locker inside the building. |
| Leasingoffice  | A Leasing office inside the building.  |
| Stairs         | A staircase inside the building.       |
| Bathroom       | A Bathroom inside the building.        |
| Handicapramp   | A Handicap ramp in the building.       |

Here is the sample json with all the data.

{% file src="/files/dPyqXZfVZpnHDJInPQdG" %}


# Data Quality

<figure><img src="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2F0UfHMtXzv1ZJIERGuIht%2FData%20quality.png?alt=media&amp;token=e6ea99e9-b1f9-41a1-8a6c-44f527a64155" alt=""><figcaption></figcaption></figure>

At Stoovo, our commitment to addressing data quality is unwavering. To uphold this unparalleled standard of excellence, we incorporate the following strategies:

* **Standardization**: All address data adheres to a uniform structure, facilitating easy ingestion, comparability, and compatibility.
* **Aggregation**: By sourcing address data from many distinct sources, we can continuously cross-check and validate for utmost accuracy.
* **Spam Filtering**: We prioritize quality over quantity. Our meticulous spam filtering protects you from dubious or irrelevant data. While we encounter significant noise in the data we collect, we take pride in delivering a pristine dataset with a 0% spam rate.
* **Geocoding**: Stoovo emphasizes precision in geocoding. By integrating multiple services, we achieve a remarkable 97% accuracy rate, surpassing competitors by about 13%. We cross-reference address data to ensure details are spot-on, preventing misdirection. In our philosophy, small refinements translate to major impacts.
* **De-duplication**: We're resolute in eliminating redundancy. If, for example, two delivery drivers and a tenant relay identical information about a building, our system efficiently integrates these details, ensuring the final record is comprehensive and accurate.
* **Ranking**: Each address is subjected to our intricate quality scoring system. Addresses that don't meet our stringent quality benchmark are meticulously reviewed manually and in person, aided by our expansive 100K+ user network. Among the critical metrics we evaluate are spam rates, frequency of duplicated addresses, geolocation accuracy, and competitive comparisons.

Our steadfast dedication to address data quality is reinforced by our Vision A.I and Machine learning models working tirelessly.


# Boundaries

<figure><img src="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2FbF9fNI1rSRD3N6sLI4Xw%2FBoundries.png?alt=media&amp;token=dbc2f476-282a-4d1a-83f3-51e1de7e60d3" alt=""><figcaption></figcaption></figure>

Stoovo's Building Boundary provides comprehensive polygonal representations of building footprints, encapsulating the precise boundaries of structures. <mark style="color:blue;">Covering 98% of buildings across the U.S</mark>., our API grants access to detailed geometrical outlines that trace the exact perimeters of buildings.

**Advantages**:

1. **Precision & Coverage**: With 98% of U.S. buildings in our database, partners can confidently access nearly exhaustive and accurate building footprint data.
2. **Enhanced Geospatial Analysis**: The polygonal data allows for more intricate geospatial analyses, from delivery services and urban planning to real estate assessments.
3. **Resource Optimization**: Companies in logistics, real estate, or infrastructure planning can optimize routing, site selection, and more by leveraging exact building boundaries.
4. **High-Quality Data Assurance**: Rigorous data verification processes ensure the building boundaries are consistently up-to-date and accurate, minimizing potential discrepancies or outdated information.

By integrating Stoovo's API, partners are empowered with high-definition spatial data, setting the foundation for smarter decision-making and enhanced operational efficiencies.


# Entrances

<figure><img src="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2F9CZOFuysKKQF2OSfEXOn%2FEntrances.png?alt=media&amp;token=e13a5bf6-6c91-40a8-9bce-cd8454e6aebb" alt=""><figcaption></figcaption></figure>

Stoovo's address API offers meticulous location data pinpointing buildings' precise entrance and exit points. This granularity extends beyond mere building footprints, diving into the specifics of entry and egress, an essential aspect for various applications.

**Advantages**:

1. **Precision Access**: Our API doesn't just stop at the building boundary; it drills down to the exact spots where one can enter or leave, ensuring unambiguous location data.
2. **Tailored for Deliveries**: For delivery companies, knowing the exact entrance saves precious minutes, reduces confusion, and enhances the overall efficiency of delivery routes. No more guessing or circling the building!
3. **Critical for Emergency Services**: In emergencies, every second counts. Whether it's a fire brigade, ambulance, or police service, having precise entrance and exit data can be life-saving. It ensures rapid response without the loss of crucial moments identifying access points.
4. **Continuous Updates**: Buildings change, and so do access points. Our rigorous data verification and update processes ensure the entrance and exit data remains contemporary and accurate.
5. **Operational Excellence**: Beyond emergency and delivery services, any operation that requires building access - from maintenance to utilities - can significantly benefit from this precise data, optimizing tasks and appointments.


# Parking Spots

<figure><img src="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2FObNcQKKThVXxVnfrpXqC%2FParkings.png?alt=media&amp;token=e4832931-5b3a-4f9e-8494-f3b17b2a1462" alt=""><figcaption></figcaption></figure>

Stoovo's API provides a sophisticated solution for locating suitable parking spots and temporary halt points specifically tailored for delivery workers. Our API delivers insights into optimal and efficient spots for short-term stops and longer-term parking.

**Advantages**:

1. **Optimized for Deliveries**: Delivery workers often grapple with finding the most convenient spots for quick drop-offs or pick-ups. Our API reduces this hassle, pointing to the nearest and most suitable parking or temporary stop, ensuring timely deliveries and reduced idle time.
2. **Green Parking Stops**: In collaboration with city administrations, Stoovo highlights green parking spots. These eco-friendly zones are designed to reduce environmental impact, support sustainable urban planning, and ensure delivery operations align with city regulations and green initiatives.
3. **Real-time Updates**: Urban dynamics change swiftly. Our API is continuously updated to reflect current availability and conditions, ensuring delivery workers aren't led to occupied or inaccessible spots.
4. **Strategic Planning**: Companies can strategically plan delivery routes, optimizing fuel usage and time, leading to cost savings and improved service delivery.
5. **Collaboration with Cities**: Our partnership with city administrations ensures the data is accurate and in tandem with urban development plans and regulations. This fosters a harmonious relationship between delivery operations and city objectives.


# Delivery Durations

<figure><img src="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2FZN9Kvl8aHmsEoHJwzOIi%2FDuration.png?alt=media&amp;token=ac06983f-872b-48a0-8fa1-c5892c3d5688" alt=""><figcaption></figcaption></figure>

Stoovo's API is designed to offer precise predictions on delivery durations to specific locations. By analyzing historical and real-time data, our system calculates the average time delivery drivers take to reach and deliver to a given address, thus providing stakeholders with a reliable estimate.

**Advantages**:

1. **Enhanced Predictability**: By understanding average delivery times, businesses can offer customers more accurate delivery window estimates, improving customer satisfaction.
2. **Optimized Scheduling**: Companies can fine-tune their delivery schedules based on the data, ensuring better resource allocation and maximizing the number of deliveries per day.
3. **Resource Efficiency**: Understanding delivery times aids in minimizing idle times for drivers and ensures better fuel and time management.
4. **Strategic Route Planning**: Knowing the average time to specific locations allows for better route optimization, potentially bypassing traffic bottlenecks or other delays.
5. **Data-Driven Decisions**: The insights derived from the Delivery Time Estimation API empower businesses to make informed decisions, from staffing levels to delivery charges.


# Accesibility POI

<figure><img src="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2F6L60D7ie7R7uD2ARi9KU%2FAccessibility.png?alt=media&amp;token=66a660ee-c935-4643-81cf-03ebdad2f23a" alt=""><figcaption></figcaption></figure>

Stoovo's API delivers detailed insights into the accessibility features of buildings, highlighting critical components such as handicap parking spots, accessible doors, ramps, and more. This specialized data ensures that every user's needs are considered and met, enhancing inclusivity in urban spaces.

**Advantages**:

1. **Inclusivity at Forefront**: By identifying and marking accessibility points, businesses, and public spaces ensure that they cater to all individuals, regardless of their mobility challenges.
2. **Enhanced User Experience**: Providing clear information on accessibility features improves the experience for disabled individuals, making their visits more comfortable and hassle-free.
3. **Regulatory Compliance**: Many jurisdictions have regulations demanding accessibility features in public spaces. Stoovo's API helps businesses stay compliant by providing clear insights into existing features.
4. **Strategic Planning**: For architects, builders, and city planners, understanding existing accessibility features aids in designing more inclusive spaces in future projects.
5. **Efficient Navigation**: For mobility-impaired individuals or those aiding them, having precise information about accessible entrances, parking, and more means less time spent searching and more time enjoying the destination.


# Indoor Direction

<figure><img src="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2FOU6xGhjW4ygWtX7v0vSa%2FIndoor.png?alt=media&amp;token=5f7416e9-126d-433c-8c78-5025e7d5663a" alt=""><figcaption></figcaption></figure>

Stoovo's API also helps navigate users seamlessly within buildings. It pinpoints key points of interest, including leasing offices, delivery lockers, elevators, stairs, and more, providing users with step-by-step guidance within complex indoor spaces.

**Advantages**:

1. **Efficient Wayfinding**: No more getting lost in expansive buildings or complexes. Users are provided clear, step-by-step directions to their desired destination within the structure.
2. **Time Savings**: Deliveries to lockers, visits to leasing offices, or locating elevators become quicker, resulting in saved time for businesses and individuals.
3. **Enhanced User Experience**: Whether a first-time visitor or a regular, the ease of indoor navigation significantly improves the overall experience within the building.
4. **Safety Benefits**: In emergencies, quickly navigating to exits or safety zones can be life-saving.
5. **Resource Optimization**: Ensuring that staff or clients can quickly locate key POIs for businesses operating within large buildings enhances operational efficiency.


# Delivery Instructions

<figure><img src="https://3967411113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmLBivpzFOJ0o6KmAqWc6%2Fuploads%2Ff5ae4440SItmH4cl6PDy%2FDelivery%20instructions%20(2).png?alt=media&amp;token=e08fdb78-6d56-4e52-8031-0ab06791c1b6" alt=""><figcaption></figcaption></figure>

Stoovo's API offers comprehensive and up-to-date guidance on facilitating deliveries for individual buildings. Recognizing that each structure has unique requirements and protocols, this API provides clear, current, and building-specific instructions for seamless delivery processes.

**Advantages**:

1. **Tailored Guidance**: Specific instructions for each building eliminate the guesswork, ensuring delivery personnel can effortlessly navigate complex building protocols.
2. **Time-Efficient Deliveries**: With precise information, delivery personnel can expedite their process, reducing time spent searching for drop-off points or navigating building intricacies.
3. **Enhanced Accuracy**: The risk of misplaced or wrongly delivered packages is significantly reduced when delivery personnel are well-informed.
4. **Dynamic Updates**: Building policies or protocols can change in an ever-evolving urban landscape. Our API ensures that users have access to the most current instructions.
5. **Improved Customer Satisfaction**: End recipients experience quicker and more accurate deliveries, enhancing satisfaction and reducing complaints.
6. **Reduction in Redelivery Attempts**: Accurate delivery instructions can drastically cut down on failed first-time deliveries, ensuring that packages reach their intended recipients on the initial attempt.
7. **Feedback Loop**: The API can be configured to allow feedback from delivery personnel, ensuring continuous refinement and accuracy of instructions.

<br>


# Demo Enpoints

Contact support to get access to demo endpoint tokens

#### Base URL: `https://geo-srv-002.stoovo.com`

#### API Endpoint: `/demo/details`

* **Method**: POST
* **Description**: Retrieves detailed information for the demo.
* #### Headers
  * **token**: `<your_access_token_here>`

    Make sure to replace `<your_access_token_here>` with the access token provided to you by the sales team. This token is required for authentication and authorization purposes when making a request to the API endpoint.
* **Request Body**:&#x20;

  ```markdown
  ### Request Body

  - `id`: The unique identifier for the object.
  - `kind`: The type or kind of the id. e.g place/restuarant (generally it is place)
  ```
* **Responses**:
  * #### API Response Example
    * Upon successfully processing a request, our API responds with a `200 OK` status code and a JSON payload detailing information about a specified location. Below is an illustrative example of such a response:
  * <pre class="language-json" data-full-width="false"><code class="lang-json"><strong>{
    </strong>    "kind": "place",
        "markerId": "64389905d21459db0b0c1555",
        "createdAt": "2024-02-27T21:02:20.578Z",
        "geometry": {
            "coordinates": [
                -122.4239107,
                37.7723322
            ],
            "type": "Point"
        },
        "isBuilding": true,
        "properties": {
    <strong>        "address": "21 Octavia St, San Francisco, CA 94102",
    </strong>        "kind": "place",
            "name": "21 Octavia St",
            "text": "21 Octavia St",
            "usermodified": false,
            "amenities": {
                "wheelchair": false,
                "elevator": false,
                "deliveryScore": 0,
                "score": 0
            },
            "delivery_time": null,
            "photos": [
                "https://placesphotos.stoovo.com/place/ChIJ3Q-piZ-AhYAR_8uZfUAXAPQ/main/default.png"
            ],
            "correct": 0,
            "incorrect": 0,
            "userReaction": 0,
            "completeData": false,
            "userReview": false,
            "types": [
                "street_address"
            ],
            "isOpenNow": null
        },
        "type": "Feature",
        "demo": true,
        "id": "64389905d21459db0b0c1555"
    }
    </code></pre>
    * This JSON object comprehensively details several attributes associated with the location, including its type, creation date, geographic details, building status, and various other properties like address, name, amenities, and photos, offering a complete overview for client usage.
  * **401 Not Authorized**
    * This status code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource. The server may require HTTP authentication (presented in WWW-Authenticate header fields), or some other form of client identification.

#### API Endpoint: `/demo/parking`

* **Method**: POST
* **Description**: Retrieves detailed information for parking and entrance facilities.
* #### Headers
  * **token**: `<your_access_token_here>`

    Ensure your request header includes a valid access token, provided by the sales team, for authentication.
* **Request Body**:

  <pre class="language-markdown"><code class="lang-markdown"><strong>### Request Body
  </strong>
  - `id`: The unique identifier for the object(address).
  - `kind`: The type or kind of the id. e.g place/restuarant (generally it is place)
  </code></pre>
* **Responses**:
  * #### API Response Example
    * Successful requests are confirmed with a `200 OK` status, returning details about the parking or entrance, as shown in the JSON example below:
    * ```json
      {
          "features": [
              {
                  "geometry": {
                      "type": "Point",
                      "coordinates": [
                          -122.01190331265741,
                          37.39659053580344
                      ]
                  },
                  "properties": {
                      "text": null,
                      "kind": "parking",
                      "id": "1698883019886.6542e5cba07ec243429a25b3",
                      "subKind": null
                  },
                  "type": "Feature"
              },
              {
                  "geometry": {
                      "type": "Point",
                      "coordinates": [
                          -122.01168280281269,
                          37.39669350114852
                      ]
                  },
                  "properties": {
                      "text": null,
                      "kind": "parking",
                      "id": "1707207468232.65c1eb2c7a72fd0d7b03eb0e",
                      "subKind": null
                  },
                  "type": "Feature"
              },
              {
                  "geometry": {
                      "type": "Point",
                      "coordinates": [
                          -122.01172276498929,
                          37.39627203238945
                      ]
                  },
                  "properties": {
                      "text": null,
                      "kind": "parking",
                      "id": "1710738221188.65f7cb2d498450a68aa084b4",
                      "subKind": null
                  },
                  "type": "Feature"
              }
          ],
          "type": "FeatureCollection"
      }
      ```
  * **401 Not Authorized**
    * Indicates failure due to invalid credentials, requiring proper authentication to access the information.

#### API Endpoint: `/demo/entrance`

* **Method**: POST
* **Description**: Retrieves detailed information for parking and entrance facilities.
* #### Headers
  * **token**: `<your_access_token_here>`

    Ensure your request header includes a valid access token, provided by the sales team, for authentication.
* **Request Body**:

  ```markdown
  ### Parameters

  - `id`: The unique identifier for the object(address).
  - `kind`: The type or kind of the id. e.g place/restuarant (generally it is place)
  ```
* #### API Response Example
  * Successful requests are confirmed with a `200 OK` status, returning details about the parking or entrance, as shown in the JSON example below:
  * ```json
    {
        "features": [
            {
                "geometry": {
                    "type": "Point",
                    "coordinates": [
                        -122.01190331265741,
                        37.39659053580344
                    ]
                },
                "properties": {
                    "text": null,
                    "kind": "entrances",
                    "id": "1698883019886.6542e5cba07ec243429a25b3",
                    "subKind": null
                },
                "type": "Feature"
            },
            {
                "geometry": {
                    "type": "Point",
                    "coordinates": [
                        -122.01168280281269,
                        37.39669350114852
                    ]
                },
                "properties": {
                    "text": null,
                    "kind": "entrances",
                    "id": "1707207468232.65c1eb2c7a72fd0d7b03eb0e",
                    "subKind": null
                },
                "type": "Feature"
            },
            {
                "geometry": {
                    "type": "Point",
                    "coordinates": [
                        -122.01172276498929,
                        37.39627203238945
                    ]
                },
                "properties": {
                    "text": null,
                    "kind": "entrances",
                    "id": "1710738221188.65f7cb2d498450a68aa084b4",
                    "subKind": null
                },
                "type": "Feature"
            }
        ],
        "type": "FeatureCollection"
    }
    ```
* **401 Not Authorized**
  * Indicates failure due to invalid credentials, requiring proper authentication to access the information.

#### API Endpoint: `/demo/units`

* **Method**: POST
* **Description**: Retrieves detailed information for various units for a address
* #### Headers
  * **token**: `<your_access_token_here>`

    Ensure your request header includes a valid access token, provided by the sales team, for authentication.
* #### Request Body:

{% code fullWidth="false" %}

```markdown
### Request Body

- `id`: The unique identifier for the object(address).
- `kind`: The type or kind of the id. e.g place/restuarant (generally it is place)
```

{% endcode %}

* **Responses**:
  * **200 OK**
    * Successful requests will return detailed information about the units, as shown in the example below:
    * ```json
      {
          "type": "FeatureCollection",
          "features": [
              {
                  "markerId": "u-705a0c7e5b5470009e3abc48aa050f40-102",
                  "parentPlaceId": "6439c1a8d21459db0b92ed0c",
                  "geometry": {
                      "type": "Point",
                      "coordinates": [
                          -122.01140190442182,
                          37.3965722416235
                      ]
                  },
                  "properties": {
                      "address": "610 E WEDDELL DR, Sunnyvale CA 94089",
                      "unit": 102,
                      "floor": 1,
                      "kind": "unit"
                  },
                  "type": "Feature"
              },
              ...
          ]
      }
      ```
  * **401 Not Authorized**
    * Indicates the request failed due to invalid credentials, requiring proper authentication.

***

***


