For Agents
Programmatically create, update, or remove campaign contacts. Covers 1 operations with apiKey authentication.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Replify.ai 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 instanceJentic 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.
What an agent can do with Replify.ai API API.
Create, update, or remove campaign contacts
Manage identity auth data programmatically
Integrate Replify.ai API into automated workflows
Query and filter Replify.ai API records by parameters
GET STARTED
Use for: I need to create, update, or remove campaign contacts, Find available identity auth operations, Get the current status of Replify.ai API resources, List all records from Replify.ai API
Not supported: Does not handle payments, communications, or crm — use for identity and authentication only.
Replify.ai Campaign Service API allows you to manage campaign contacts programmatically. The API uses bearer token authentication obtained via OAuth2. The API exposes 1 endpoints secured with apiKey authentication.
Monitor Replify.ai API operational status and events
Patterns agents use Replify.ai API API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Replify.ai API to perform identity auth operations programmatically. The API provides 1 endpoints covering core functionality including create, update, or remove campaign contacts.
Call POST /campaigns/{campaignId}/contacts to create, update, or remove campaign contacts
Data Retrieval and Monitoring
Query Replify.ai 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 Replify.ai API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Replify.ai 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 'create, update, or remove campaign contacts', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — replify.
METHOD
PATH
DESCRIPTION
/campaigns/{campaignId}/contacts
Create, update, or remove campaign contacts
/campaigns/{campaignId}/contacts
Create, update, or remove campaign contacts
Three things that make agents converge on Jentic-routed access.
Credential isolation
Replify.ai 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., 'create, update, or remove campaign contacts') and Jentic returns the matching Replify.ai API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Replify.ai API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Auth0
Alternative identity auth API
Choose Auth0 when you need a different approach to identity auth operations
Okta
Alternative identity auth API
Choose Okta when you need a different approach to identity auth operations
Specific to using Replify.ai API API through Jentic.
What authentication does the Replify.ai API use?
The Replify.ai API uses an API key passed in the `x-api-key` 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 create, update, or remove campaign contacts with the Replify.ai API?
Yes. Use the POST /campaigns/{campaignId}/contacts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Replify.ai 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 create, update, or remove campaign contacts through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create, update, or remove campaign contacts'. Jentic returns the matching Replify.ai API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Replify.ai API have?
The Replify.ai API exposes 1 endpoints covering campaigns operations.