nodaFi API

Name: nodaFi API API
Brand: nodaFi API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsProject Managementbearer1 EndpointsREST

For Agents

Run facility-management operations on nodaFi — work orders, assets, locations, inspections — through a single authenticated GraphQL endpoint at /graphql.

Quickstart

Get started with nodaFi API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list nodafi work orders"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with nodaFi API API.

Submit GraphQL queries and mutations to /graphql for facility-management resources

Read and update work order records via GraphQL operations against the single endpoint

Query asset, location, and vendor records using GraphQL field selection

Authenticate every request with HTTP bearer tokens issued from the nodaFi dashboard

GET STARTED

Start building with nodaFi API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for nodaFi API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for nodaFi API, keeping it validated and agent-ready. nodaFi is a facility-management platform that exposes its full surface through a single GraphQL endpoint at /graphql. All read and mutation operations — work orders, assets, locations, vendors, and inspections — flow through that POST endpoint with a typed query body. Authentication uses HTTP bearer tokens issued from the nodaFi dashboard. Because the surface is GraphQL-only, agents must compose queries rather than navigating multiple REST paths.

Use Cases

Patterns agents use nodaFi API API for, with concrete tasks.

★ Work Order Automation

Facilities teams running maintenance programs need a programmatic way to create, list, and update work orders without using the nodaFi UI. The /graphql endpoint accepts mutations to create and update work orders and queries to list open tickets per asset or location. This lets a backoffice agent triage incoming requests and feed them into nodaFi as work orders ready for technician dispatch.

POST a GraphQL mutation to /graphql that creates a work order with title, asset, location, and priority fields

Asset Inventory Sync

When a facility-management system feeds an asset inventory into financial reporting or inspection scheduling, a regular sync against nodaFi keeps the source of truth aligned. A GraphQL query against /graphql can return assets with location, type, and status fields in a single round trip. Pagination is handled inside the query body using GraphQL cursors.

POST a GraphQL query to /graphql requesting assets with id, name, locationId, and status, paginated through cursor fields

Inspection Reporting

Compliance and operations teams need exportable inspection records for audits and regulator reporting. The /graphql endpoint exposes inspection objects with fields for date, inspector, asset, and outcome, retrievable in a single query shaped to the report's columns. This avoids brittle CSV exports from the nodaFi UI.

POST a GraphQL query against /graphql for inspections within a date range and stream the response into a compliance report

AI Agent Facility Assistant

An assistant supporting facility managers can use Jentic to call nodaFi's GraphQL endpoint without composing the full HTTP request by hand. Jentic loads the /graphql operation schema with a body parameter for the GraphQL query string, injects the bearer token, and returns the typed response. The same agent can chain multiple GraphQL queries for a single user intent.

Use Jentic to POST /graphql with a query that lists open work orders for a building and returns the result to the calling agent

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for nodafi api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/graphql

Single GraphQL endpoint for all nodaFi queries and mutations

POST

/graphql

Single GraphQL endpoint for all nodaFi queries and mutations

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

nodaFi bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access — the raw token never enters the agent context, and rotation is handled by Jentic without code changes.

Intent-based discovery

Agents search by intent (e.g. 'list nodafi work orders' or 'create a nodafi inspection') and Jentic routes the call to the /graphql endpoint with a pre-shaped GraphQL query string in the request body.

Time to first call

Direct integration: 1-2 days to wire bearer auth and write GraphQL query strings for each resource. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Salesforce API

Salesforce CRM and Service Cloud cases often surface facility issues that should become nodaFi work orders.

Use Salesforce alongside nodaFi when service requests are tracked in CRM and need to be pushed into a facility-management work order.

Complementary

Intercom API

Intercom support conversations often surface facility issues that should become nodaFi work orders.

Pair Intercom with nodaFi to convert customer-reported facility problems into structured work orders.

Complementary

ShipEngine API

ShipEngine handles part and replacement shipping that often accompanies facility maintenance work orders.

Use ShipEngine when a nodaFi work order requires a part shipment to a technician or site.

FAQs

Specific to using nodaFi API API through Jentic.

Why is there no official OpenAPI spec for nodaFi API?

nodaFi exposes a GraphQL-only API and does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call nodaFi API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the nodaFi API use?

nodaFi uses HTTP bearer authentication. Pass the bearer token issued from the nodaFi dashboard in the Authorization header. Through Jentic the token is held in the vault and injected at call time.

Can I create work orders with the nodaFi API?

Yes. Submit a GraphQL mutation to POST /graphql that creates a work order with the required fields (title, asset, location, priority). The response returns the created work order id.

What are the rate limits for the nodaFi API?

The OpenAPI spec does not declare specific rate limits. nodaFi enforces account-tier quotas — Jentic surfaces 429 responses with backoff so retries are paced correctly.

How do I run a GraphQL query against nodaFi through Jentic?

Run pip install jentic, search Jentic for 'query nodafi work orders', load the /graphql operation, place your GraphQL query string in the request body, and execute. Jentic injects the bearer token and returns the typed response.

Is the nodaFi API a REST API?

No. nodaFi exposes a single GraphQL endpoint at POST /graphql. All read and write operations flow through that endpoint with a query string in the body, rather than per-resource REST paths.