canonical: https://jentic.com/apis/swaggerhub.enable-networks/address-api

# Enable Networks Address API

Update proactive value based on the current proactive value calculated from the combination of work order type and primary incident type. Before you can access the production APIs, you need to complete the production onboarding process. Note, the production URI will be https://apis.enable.net.nz/address/v1. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get_proactive, put_proactive. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- GET_proactive
- PUT_proactive
- Integrate Address API into automated workflows
- Query and filter Address API records by parameters
- Monitor Address API operational status and events

## Use cases

### E-Commerce Operations

Use the Address API to perform e commerce operations programmatically. The API provides 2 endpoints covering core functionality including get_proactive, put_proactive.

Example prompt: Call GET /proactive/{fsl_id} to get_proactive

### Data Retrieval and Monitoring

Query Address API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Address API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Address API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get_proactive', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /proactive/{fsl_id} | GET_proactive |
| PUT | /proactive/{fsl_id} | PUT_proactive |

## Key resources

- **Proactive** — Operations for proactive

## Why Jentic

- **Setup:** Wiring the Address API by hand means supplying its Okta-verified bearer token in the Authorization header, targeting the correct Enable Networks host, and handling responses yourself. Through Jentic you install once, import the Address API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Address API puts the service location id in the URL path (/proactive/{fsl_id}), so a rule can pin your agent to one service location: it can read and update the proactive record for that location and nothing else. You choose the operations it may call, so the update operation is not included unless you add it.
- **Credential handling:** Your Address API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get the proactive record for a service location', and Jentic returns the matching Address API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Address API use?

The Address API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get_proactive with the Address API?

Yes. Use the GET /proactive/{fsl_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Address API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get_proactive through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get_proactive'. Jentic returns the matching Address API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Address API have?

The Address API exposes 2 endpoints covering proactive operations.

### Can I limit what my agent is allowed to do with the Address API?

Yes. Jentic One is self-hosted, so your own rules decide which Address API operations and credentials the agent may use. Because the service location id sits in the URL path (/proactive/{fsl_id}), you can pin the agent to a single location and grant only GET /proactive/{fsl_id} so it reads that proactive record but cannot change it, adding PUT /proactive/{fsl_id} only when you want it to update. The stored API key is injected at execution time under those rules, so the agent can only call the operations you approve.