Address API

Name: Address API API
Brand: Address API
Availability: InStock

★ Only Publicly Available SpecE CommerceStorefrontapiKey2 EndpointsREST

For Agents

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

Use for: I need to get_proactive, I want to put_proactive, Get the current status of Address API resources, List all records from Address API

Quickstart

Get started with Address 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:
"get_proactive"

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

Capabilities

What an agent can do with Address API API.

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

GET STARTED

Start building with Address API API

Explore with Jentic

View OpenAPI Spec

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

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.

Use Cases

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

★ 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.

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.

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.

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

Key Endpoints

2 endpoints — update proactive value based on the current proactive value calculated from the combination of work order type and primary incident type.

METHOD

PATH

DESCRIPTION

GET

/proactive/{fsl_id}

GET_proactive

PUT

/proactive/{fsl_id}

PUT_proactive

GET

/proactive/{fsl_id}

GET_proactive

PUT

/proactive/{fsl_id}

PUT_proactive

Why though Jentic?

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

Credential isolation

Address API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get_proactive') and Jentic returns the matching Address API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Address API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Address API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.