> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-graphql-api/business-data-repository/overview.md).

# Business Data Repository overview

Business Data Repository manages assets, devices, geo objects, schedules, custom fields, and catalogs through Navixy GraphQL API.

{% hint style="warning" %}
**Navixy GraphQL API is a work in progress.** This documentation is published for preview purposes only and doesn't reflect a stable release. Structure, field names, and behaviors are subject to change.
{% endhint %}

**Business Data Repository** is the product that manages the business entities of the Navixy platform. It is one of the products served by [Navixy GraphQL API](/docs/navixy-graphql-api/readme.md). It defines what you track (assets), how data is collected (devices), where important points are located (geo objects), and when things happen (schedules).

All Business Data Repository operations are nested under the `bdr` field of the `Query` and `Mutation` types. The shared pages of this space cover the request format, [authentication](/docs/navixy-graphql-api/authentication.md), [pagination](/docs/navixy-graphql-api/pagination.md), and [error handling](/docs/navixy-graphql-api/error-handling.md). For your first request, see [Getting started](/docs/navixy-graphql-api/getting-started.md).

## Purpose and capabilities

Business Data Repository enables you to:

* Create **assets** and organize them into **groups**
* Register **devices** (GPS trackers, sensors) with hardware identifiers and add them to **inventories**
* Define **geo objects** (geofences, points of interest, routes) with GeoJSON geometry
* Create **schedules** for work hours, maintenance windows, and time-based rules
* Configure **custom fields** to store your own workspace-specific data on assets and geo objects

## Key concepts

The product is organized around the following core resources:

<table><thead><tr><th width="147.48895263671875">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Workspace</strong></td><td>The tenant that owns every other resource: members, assets, devices, geo objects, and schedules. Navixy Console provisions workspaces, so they are read-only in this API.</td></tr><tr><td><strong>Asset</strong></td><td>A business object you're tracking: a vehicle, piece of equipment, employee, or any other entity. Assets can be linked into <strong>asset groups</strong> or assigned one or multiple GPS devices.</td></tr><tr><td><strong>Device</strong></td><td>Physical tracking hardware (GPS tracker, sensor, beacon). Devices have types, models, statuses, and hardware identifiers (IMEI, serial number).</td></tr><tr><td><strong>Inventory</strong></td><td>A logical grouping of devices for stock management (warehouse, vehicle stock, field inventory).</td></tr><tr><td><strong>Geo object</strong></td><td>A location-based entity based on the GeoJSON standard: geofence, point of interest, or route.</td></tr><tr><td><strong>Schedule</strong></td><td>iCalendar-compatible time-based schedules for your operations (maintenance cycles, time shifts).</td></tr></tbody></table>

## Navigation

The Business Data Repository documentation has two sections: guides and the API reference.

### Guides

Step-by-step walkthroughs of the most common scenarios:

* [Managing device records and identifiers](/docs/navixy-graphql-api/business-data-repository/guides/managing-device-records-and-identifiers.md) and [Managing device inventory](/docs/navixy-graphql-api/business-data-repository/guides/managing-device-inventory.md)
* [Creating assets and assigning devices](/docs/navixy-graphql-api/business-data-repository/guides/creating-assets-and-assigning-devices.md) and [Organizing assets into groups](/docs/navixy-graphql-api/business-data-repository/guides/organizing-assets-into-groups.md)
* [Defining and using custom fields](/docs/navixy-graphql-api/business-data-repository/guides/defining-and-using-custom-fields.md), with [Custom field filtering and sorting](/docs/navixy-graphql-api/filtering-and-sorting/custom-field-filtering.md) for queries by custom field values
* [Defining recurring schedules](/docs/navixy-graphql-api/business-data-repository/guides/defining-recurring-schedules.md)
* [Creating geofences, POIs, and routes](/docs/navixy-graphql-api/business-data-repository/guides/creating-geofences-pois-and-routes.md)
* [Investigating changes with audit logs](/docs/navixy-graphql-api/business-data-repository/guides/investigating-changes-with-audit-logs.md)

### API reference

The [Business Data Repository API reference](/docs/navixy-graphql-api/business-data-repository/api-reference.md) gives the complete technical specification for the GraphQL types and operations of Business Data Repository, one page per category:

* [Workspaces](/docs/navixy-graphql-api/business-data-repository/api-reference/workspaces.md)
* [Actors](/docs/navixy-graphql-api/business-data-repository/api-reference/actors.md)
* [Devices](/docs/navixy-graphql-api/business-data-repository/api-reference/devices.md)
* [Assets](/docs/navixy-graphql-api/business-data-repository/api-reference/assets.md)
* [Geo objects](/docs/navixy-graphql-api/business-data-repository/api-reference/geo-objects.md)
* [Schedules](/docs/navixy-graphql-api/business-data-repository/api-reference/schedules.md)
* [Custom fields](/docs/navixy-graphql-api/business-data-repository/api-reference/custom-fields.md)
* [Audit](/docs/navixy-graphql-api/business-data-repository/api-reference/audit.md)
* [Catalogs](/docs/navixy-graphql-api/business-data-repository/api-reference/catalogs.md)

For the types that Business Data Repository shares with the other products, and for an index of the whole API, see the [Core API reference](/docs/navixy-graphql-api/core-api-reference.md).

{% hint style="warning" %}
The API supports [GraphQL introspection](/docs/navixy-graphql-api/graphql-basics.md#introspection) for authenticated users. You can also check the public [GraphQL schema](/docs/navixy-graphql-api/developer-resources/public-graphql-schema.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/navixy-graphql-api/business-data-repository/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.