Networx Public API

Name: Networx Public API
Brand: Networx Public API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbasic4 EndpointsREST

For Agents

Subscribe to Networx home-services lead webhooks and validate credentials so an agent receives new leads in real time without polling.

Install Jentic One Beta

Connect the Networx Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Networx Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetworx.com%2Fnetworx" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetworx.com%2Fnetworx" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Networx Public API.

Subscribe a webhook URL to receive new home-services lead notifications from the Networx marketplace

Unsubscribe an existing webhook subscription by its subscription identifier

Validate Networx Basic Auth credentials before establishing a webhook subscription

GET STARTED

Start building with Networx Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Networx Public API for, with concrete tasks.

★ Real-Time Home Services Lead Routing

Contractors and lead-management platforms subscribe to Networx webhook events so new home-improvement leads are pushed into their CRM or dispatch system the moment a homeowner submits a request. The integration uses POST /public/subscription to register a callback URL secured with Basic Auth, eliminating polling and reducing speed-to-lead from minutes to seconds.

Call POST /public/subscription with the contractor's CRM webhook URL and Basic Auth credentials, then confirm receipt by triggering GET /public/test_trigger and verifying the test payload arrived.

Integration Credential Validation

Before going live, integrators verify that the Basic Auth credentials issued by Networx are accepted using GET /public/validate. This catches misconfigured environment variables and rotated passwords during deployment rather than failing silently when real leads arrive.

Send GET /public/validate with the configured Basic Auth header and surface a clear error if the response status is not 200 so the deployment pipeline can block release.

Sandbox Webhook Development

Developers building a new Networx integration call GET /public/test_trigger to receive a representative lead payload without waiting for real homeowner traffic. This lets them shape database schemas, build CRM mapping logic, and exercise error handling against realistic data before turning on the production subscription.

Invoke GET /public/test_trigger, parse the returned lead JSON, and seed a local database table so downstream CRM mapping logic can be unit tested.

AI Agent Lead Distribution

An AI agent operating a contractor's intake workflow uses Jentic to discover the Networx subscribe operation, register a webhook tied to the agent's own ingestion endpoint, and then triage each incoming lead automatically - qualifying, scoring, and assigning to the correct technician without human intervention.

Use Jentic to search 'subscribe to home services leads', load the Networx subscribe schema, execute POST /public/subscription with the agent's ingestion URL, then route each subsequent webhook payload to the qualification workflow.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/public/validate

Validate Basic Auth credentials

POST

/public/subscription

Subscribe a new webhook for lead events

DELETE

/public/subscription/{subscription_id}

Unsubscribe an existing webhook

GET

/public/test_trigger

Retrieve example lead data for testing

GET

/public/validate

Validate Basic Auth credentials

POST

/public/subscription

Subscribe a new webhook for lead events

DELETE

/public/subscription/{subscription_id}

Unsubscribe an existing webhook

GET

/public/test_trigger

Retrieve example lead data for testing

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Networx Public API by hand means encoding its HTTP basic username and password, targeting the www.networx.com host, and managing lead-delivery webhook subscriptions yourself. Through Jentic you install once, import Networx from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Networx puts the subscription id in the URL path (/public/subscription/{subscription_id}), so a rule can pin your agent to one subscription. You choose the operations it may call, so deleting a subscription is not included unless you add it.

Credential isolation

Your Networx basic auth username and password are stored once, encrypted, by your own Jentic One instance and injected at execution time as the basic auth header. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'subscribe to home services leads' or 'validate a subscription', and Jentic returns the matching Networx operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Networx Public API through Jentic.

Why is there no official OpenAPI spec for Networx Public API?

Networx does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Networx Public API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Networx Public API use?

The Networx Public API uses HTTP Basic Auth - a username and password pair sent base64-encoded in the Authorization header. Through Jentic, these credentials are stored in the encrypted Jentic One instance and never enter the agent's context window.

Can I subscribe to home-services leads with the Networx Public API?

Yes. Call POST /public/subscription with a callback URL and Networx pushes new lead payloads to that URL as homeowners submit requests. Use DELETE /public/subscription/{subscription_id} to remove the subscription when no longer needed.

What are the rate limits for the Networx Public API?

Networx does not document explicit numeric rate limits in the spec. Because the API is webhook-driven rather than polled, normal usage involves only one subscribe call per integration plus occasional credential validation, so limits rarely apply.

How do I test a Networx webhook integration through Jentic?

Use Jentic to search 'get networx test lead', load the GET /public/test_trigger schema, and execute it. The endpoint returns a representative lead payload you can use to develop and verify your webhook handler before subscribing in production.

Is the Networx Public API free?

Access to the Networx Public API requires an active Networx contractor or partner account - credentials are issued by Networx as part of the commercial relationship, not self-served.

Can I limit what my agent is allowed to do with the Networx Public API?

Yes. Jentic One is self-hosted, so you set the rules that decide which Networx operations and credentials your agent may use. You can allow only the calls you want, such as GET /public/validate and POST /public/subscription, while excluding DELETE /public/subscription/{subscription_id} so the agent cannot cancel a webhook. Because the subscription id sits in the URL path, a rule can also pin the agent to a single subscription rather than any it might name.