Webconnex API

Name: Webconnex API
Brand: Webconnex API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey32 EndpointsREST

For Agents

Programmatically health check, search orders. Covers 32 operations with apiKey authentication.

Use for: I need to health check, I want to orders, Search for order by id, Find all registrants

Install Jentic One Beta

Connect the Webconnex API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Webconnex 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Webconnex API.

Health check

Search orders

Get order by ID

Check in registrant

GET STARTED

Start building with Webconnex API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Webconnex API for, with concrete tasks.

★ Payments Operations

Use the Webconnex API to perform payments operations programmatically. The API provides 32 endpoints covering core functionality including health check, search orders, get order by id.

Call GET /ping to health check

Automated Coupons Management

Automate coupons operations by combining multiple Webconnex API endpoints. Agents can search orders and then get order by id in a single workflow.

Call GET /search/orders to search orders, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Webconnex 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 'health check', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

32 endpoints — webconnex (used by redpodium) provides apis for managing orders, registrants, tickets, subscriptions, transactions, customers, forms, coupons, and webhooks.

METHOD

PATH

DESCRIPTION

GET

/ping

Health check

GET

/search/orders

Search orders

GET

/search/orders/{id}

Get order by ID

GET

/search/registrants

Search registrants

GET

/search/registrants/{id}

Get registrant by ID

POST

/registrant/check-in

Check in registrant

POST

/registrant/check-out

Check out registrant

GET

/search/tickets

Search tickets

GET

/ping

Health check

GET

/search/orders

Search orders

GET

/search/orders/{id}

Get order by ID

GET

/search/registrants

Search registrants

GET

/search/registrants/{id}

Get registrant by ID

POST

/registrant/check-in

Why Jentic?

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

Credential isolation

Webconnex 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., 'health check') and Jentic returns the matching Webconnex API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

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

FAQs

Specific to using Webconnex API through Jentic.

What authentication does the Webconnex API use?

The Webconnex API uses an API key passed in the `apiKey` 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 health check with the Webconnex API?

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

What are the rate limits for the Webconnex 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 health check through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'health check'. Jentic returns the matching Webconnex API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Webconnex API have?

The Webconnex API exposes 32 endpoints covering coupons, customers, forms operations.

Webconnex API

Connect the Webconnex API to your agent

Capabilities

Start building with Webconnex API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs