> 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/products.md).

# Products

- [Business Data Repository overview](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository.md): Business Data Repository stores the business data of a workspace: assets, devices, geo objects, schedules, and your own fields and lists.
- [Guides](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides.md)
- [Activating a device](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides/activating-a-device.md): Activate a batch of GPS devices through Navixy GraphQL API, correct a wrong phone number, resend a lost SMS, and list the devices still waiting to connect.
- [Managing device records and identifiers](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides/managing-device-records-and-identifiers.md): Register and manage GPS trackers, sensors, and other hardware devices.
- [Managing device inventory](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides/managing-device-inventory.md): Create inventories, assign devices to them, transfer devices, and track assignment history.
- [Creating assets and assigning devices](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides/creating-assets-and-assigning-devices.md): Create and manage assets: vehicles, equipment, and other tracked objects.
- [Defining and using custom fields](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides/defining-and-using-custom-fields.md): Define and use custom fields to attach domain-specific data to entities.
- [Organizing assets into groups](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides/organizing-assets-into-groups.md): Organize assets into typed, color-coded collections for fleet segmentation and reporting.
- [Creating geofences, POIs, and routes](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides/creating-geofences-pois-and-routes.md): Create geofences, POIs, and routes in different shapes using GeoJSON geometry.
- [Defining recurring schedules](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides/defining-recurring-schedules.md): Create, update, query, and delete JSCalendar-aligned schedules compatible with RFC 5545 (iCalendar).
- [Investigating changes with audit logs](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/guides/investigating-changes-with-audit-logs.md): Reconstruct who changed an entity, what they changed, and when with entityHistory and auditEvents queries.
- [Business Data Repository API reference](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference.md): How the Business Data Repository reference is organized: one page per category for workspaces, actors, devices, assets, geo objects, schedules, custom fields, audit, and catalogs.
- [Workspaces](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/workspaces.md): Workspaces are isolated tenants that own all business data: members, devices, assets, geo objects, and configuration. The API acts in the workspace that your token names and exposes it read-only. Navi
- [Members](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/workspaces/members.md): Query reference for workspace members: which users belong to a workspace, whether each membership is active, and when it was assigned.
- [Actors](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/actors.md): Actors represent entities that can authenticate and perform actions in the system, including users and integrations.
- [Users](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/actors/users.md): Reference for user accounts and user-defined catalog items: the read-only User object, the me query with the organizations and workspaces the caller can switch to, and the mutations that manage hierar
- [Integrations](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/actors/integrations.md): Queries and mutations for integration accounts used by API clients, automated systems, and third-party service connections.
- [Devices](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/devices.md): Complete reference for devices: register GPS trackers and sensors, manage hardware identifiers, link devices to assets, and track relations.
- [Inventory](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/devices/inventory.md): Complete reference for device inventory. Manage warehouses, assign devices to inventory locations, and query assignment history.
- [Assets](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/assets.md): Complete reference for assets: queries, mutations, and types for the trackable business objects your workspace monitors and manages.
- [Asset groups](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/assets/groups.md): Complete reference for asset groups: group types, groups, memberships, and history.
- [Geo objects](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/geo-objects.md): Complete reference for geo objects: queries, mutations, and types for geofences, points of interest, and routes with GeoJSON geometry.
- [Schedules](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/schedules.md): Complete reference for schedules, including queries, mutations, and types for defining recurring time patterns such as working hours and maintenance windows (iCalendar-compatible).
- [Custom fields](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/custom-fields.md): Type definitions for custom field definitions, including field types, params, options, filter inputs, and the patch input used in asset and geo object mutations.
- [Audit](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/audit.md): Query the audit trail to retrieve a paginated, filterable log of entity create, update, and delete events across your workspace.
- [Catalogs](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/catalogs.md): Explains catalogs as Business Data Repository reference data, including the CatalogItem interface, item origins, display metadata, and hierarchical items.
- [Catalog items](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/catalogs/catalog-items.md): Queries, mutations, and types for catalog items, the configurable lookup entries used for device types, asset types, statuses, and other reference data.
- [Catalog reference](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/catalogs/catalog-reference.md): Cross-reference of all catalog types organized by entity. Use this page to find which catalog backs a given field.
- [Tags](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/catalogs/tags.md): Complete reference for tags. Create and manage flexible labels for classifying assets, geo objects, and other entities.
- [System catalogs](https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/catalogs/system.md): Predefined system catalog items available to all workspaces. These read-only reference types cannot be modified or deleted.
- [Tracking overview](https://navixy.com/docs/navixy-graphql-api/products/tracking.md): Tracking provides the live state of assets and their devices, the stream that follows that state, and the trips and stops calculated from device messages.
- [Guides](https://navixy.com/docs/navixy-graphql-api/products/tracking/guides.md)
- [Building a live fleet map](https://navixy.com/docs/navixy-graphql-api/products/tracking/guides/building-a-live-fleet-map.md): Show where your assets are, whether they are moving and reporting, and what their sensors say, then keep the picture current with a state stream.
- [Reading a vehicle trip history](https://navixy.com/docs/navixy-graphql-api/products/tracking/guides/reading-a-vehicle-trip-history.md): Read a vehicle's trip history with Navixy GraphQL API: request a period, receive trips and stops with totals, and load the route of each trip.
- [Tracking API reference](https://navixy.com/docs/navixy-graphql-api/products/tracking/api-reference.md): How the Tracking reference is organized: one page per concept for live state, state streams, readings and the field dictionary, and trips and stops.
- [Live state](https://navixy.com/docs/navixy-graphql-api/products/tracking/api-reference/state.md): Reference for live tracking state: the last known position, connectivity, motion, readings and events of a device, the per-device states of an asset, and the queries that read them.
- [State streams](https://navixy.com/docs/navixy-graphql-api/products/tracking/api-reference/state/streams.md): Reference for the tracking subscription: the full state of an asset, with its linked devices, pushed on every report, delivered in batches with opening-snapshot markers and removal signals.
- [Readings and the field dictionary](https://navixy.com/docs/navixy-graphql-api/products/tracking/api-reference/readings.md): Reference for tracking readings: the value model, the reading and its unit rules, and the field dictionary with the queries that expose it.
- [Trips and stops](https://navixy.com/docs/navixy-graphql-api/products/tracking/api-reference/trips.md): Reference for trips and stops: timelines derived from the message archive, the segmentation policy that cuts them, and the options that shape returned points.
- [IoT Logic overview](https://navixy.com/docs/navixy-graphql-api/products/iot-logic.md): IoT Logic in Navixy GraphQL API: create, read, update, enable, and delete the flows that process the messages of your devices.
- [How IoT Logic flows work](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/how-flows-work.md): How IoT Logic flows work in Navixy GraphQL API: how a message moves through the graph, where calculated attributes go, and how a write replaces a flow.
- [IoT Logic node types](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/node-types.md): The IoT Logic node types in Navixy GraphQL API: the fields that each type takes in a write, what it does to a message, and the rules that apply to it.
- [Flow validation errors](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/flow-validation-errors.md): Why an IoT Logic flow write fails validation, how the violations list names every problem at once, and how to fix each violation code.
- [Guides](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/guides.md): Step-by-step guides for IoT Logic in Navixy GraphQL API: building and changing flows, and handling the errors that a write returns.
- [Creating and updating flows](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/guides/creating-and-updating-flows.md): Create an IoT Logic flow through Navixy GraphQL API, read it back, replace its graph, enable it, and delete it.
- [Reading flows and device data](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/guides/reading-flows-and-device-data.md): Read IoT Logic data through Navixy GraphQL API: the attribute names of your devices, what a flow calculated, the flows of your workspace, and the flows that a device is in.
- [Calculating values in several steps](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/guides/calculating-values-in-several-steps.md): Build an IoT Logic flow through Navixy GraphQL API that calculates values in a chain of nodes: fuel in litres, then percentage and change, then a check.
- [Generating flows with an AI assistant](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/guides/generating-flows-with-an-ai-assistant.md): Rules and a checklist for an AI assistant that writes IoT Logic flows for Navixy GraphQL API: what to ask first, what to produce, and how to validate.
- [IoT Logic API reference](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/api-reference.md): How the IoT Logic reference is organized: one page for flows, with their node types, transitions, inputs, queries, and mutations.
- [Flows](https://navixy.com/docs/navixy-graphql-api/products/iot-logic/api-reference/flows.md): Reference for IoT Logic flows: the flow and its node types, transitions, the inputs that write a whole graph, and the queries and mutations for flows.
- [Billing overview](https://navixy.com/docs/navixy-graphql-api/products/billing.md): Billing stores what a workspace pays for: its plan, the usage reported for it, the invoices that charge for both, and the prepaid balance.
- [Guides](https://navixy.com/docs/navixy-graphql-api/products/billing/guides.md)
- [Choosing a plan and subscribing](https://navixy.com/docs/navixy-graphql-api/products/billing/guides/choosing-a-plan-and-subscribing.md): List the plans your workspace may subscribe to and what each one charges, subscribe your workspace to the plan you choose, and confirm the subscription.
- [Reading balance and statement](https://navixy.com/docs/navixy-graphql-api/products/billing/guides/reading-balance-and-statement.md): Read your workspace's prepaid balance, then list the payments, corrections, and invoice charges that changed it.
- [Reading usage submissions](https://navixy.com/docs/navixy-graphql-api/products/billing/guides/reading-usage-submissions.md): List the usage that Navixy products reported for your workspace, read what each submission says, and narrow the list to one metric or one period.
- [Reading invoices](https://navixy.com/docs/navixy-graphql-api/products/billing/guides/reading-invoices.md): List your workspace's invoices, read the lines of one invoice, match it to the balance statement, and find the invoices that are still unpaid.
- [Billing errors](https://navixy.com/docs/navixy-graphql-api/products/billing/errors.md): How the Billing operations use the shared error codes: what a missing entity returns, which fields a Billing error has, and the errors of the my\* operations.
- [Billing API reference](https://navixy.com/docs/navixy-graphql-api/products/billing/api-reference.md): How the Billing reference is organized: one page per topic for plans, subscriptions, balances, submissions, and invoices.
- [Plans](https://navixy.com/docs/navixy-graphql-api/products/billing/api-reference/plan.md): Reference for the plans a workspace may subscribe to: the myAvailablePlans query, the BillingAvailablePlan and BillingAvailablePlanItem types, and the product domains, metrics, and pricing vocabulary
- [Subscriptions](https://navixy.com/docs/navixy-graphql-api/products/billing/api-reference/subscription.md): Reference for workspace subscriptions: the mySubscribe mutation, the mySubscriptions query, and the subscription, filter, and order types they use.
- [Balances](https://navixy.com/docs/navixy-graphql-api/products/billing/api-reference/balance.md): Reference for the workspace balance: the one balance in USD, the statement entries that moved it, and the myBalance and myBalanceEntries queries.
- [Submissions](https://navixy.com/docs/navixy-graphql-api/products/billing/api-reference/submission.md): Reference for the usage-metric and invoice-line-item submissions of your workspace: the myUsageMetricSubmissions and myInvoiceLineItemSubmissions queries, with their filter, order, and pagination type
- [Invoices](https://navixy.com/docs/navixy-graphql-api/products/billing/api-reference/invoice.md)
- [Console overview](https://navixy.com/docs/navixy-graphql-api/products/console.md): Console shows which products your workspace has, allows you to enable or disable a product, and lists the available organizations and workspaces.
- [Guides](https://navixy.com/docs/navixy-graphql-api/products/console/guides.md)
- [Enabling and disabling a product](https://navixy.com/docs/navixy-graphql-api/products/console/guides/enabling-and-disabling-a-product.md): Read the products of your workspace, enable one that your plan covers, follow the change until it's done, and disable a product again through the Console API.
- [Console errors](https://navixy.com/docs/navixy-graphql-api/products/console/errors.md): How the Console operations use the shared error codes.
- [Console API reference](https://navixy.com/docs/navixy-graphql-api/products/console/api-reference.md): How the Console reference is organized: one page each for the organizations and the workspaces a caller can reach and for the products of a workspace, and how Console's connections paginate.
- [Organizations](https://navixy.com/docs/navixy-graphql-api/products/console/api-reference/organizations.md): Reference for the organizations a caller can reach through Navixy Console: the accessibleOrganizations query and the ConsoleOrganization type with its connection.
- [Workspaces](https://navixy.com/docs/navixy-graphql-api/products/console/api-reference/workspaces.md): Reference for the workspaces a caller can reach through Navixy Console: the accessibleWorkspaces query and the ConsoleWorkspace type with its connection.
- [Members](https://navixy.com/docs/navixy-graphql-api/products/console/api-reference/members.md): Reference for the members of your organization as Navixy Console reports them: the members query, the ConsoleMember type with what you may do to each member, and its connection.
- [Products](https://navixy.com/docs/navixy-graphql-api/products/console/api-reference/products.md): Reference for the products of a workspace: the workspaceProducts, productCatalog, and workspaceOperation queries, the workspaceProductEnable and workspaceProductDisable mutations, and the types they u
- [IAM overview](https://navixy.com/docs/navixy-graphql-api/products/iam.md): IAM holds the roles of your organization. The API lets you view, create, and change roles, and assign them to members or revoke them.
- [IAM API reference](https://navixy.com/docs/navixy-graphql-api/products/iam/api-reference.md): How the IAM reference is organized: one page each for roles, for what a role grants, and for who holds a role, and how the IAM lists paginate.
- [Roles](https://navixy.com/docs/navixy-graphql-api/products/iam/api-reference/roles.md): Reference for the roles of your organization: the roles, role, and workspaceRoles queries, the roleCreate, roleUpdate, and roleDelete mutations, and the IamRole type with its connection.
- [Role access](https://navixy.com/docs/navixy-graphql-api/products/iam/api-reference/role-access.md): Reference for what a role grants: the workspaces it reaches, and the products, features, and data resources it covers, with the matching input types.
- [Role assignments](https://navixy.com/docs/navixy-graphql-api/products/iam/api-reference/role-assignments.md): Reference for role assignments in your organization: the memberRoles and roleHolders queries, the memberRoleAssign and memberRoleRevoke mutations, and the holder and assignment types.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/navixy-graphql-api/products.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.