Plezi API

Name: Plezi API
Brand: Plezi API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey13 EndpointsREST

For Agents

Programmatically verify authentication, list contact fields. Covers 13 operations with apiKey authentication.

Use for: I need to verify authentication, I want to contact fields, Search for a contact, Find all contacts

Install Jentic One Beta

Connect the Plezi API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Plezi 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 Plezi API.

Verify authentication

List contact fields

Create a contact

Export all contacts

GET STARTED

Start building with Plezi API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Plezi API for, with concrete tasks.

★ Payments Operations

Use the Plezi API to perform payments operations programmatically. The API provides 13 endpoints covering core functionality including verify authentication, list contact fields, create a contact.

Call GET / to verify authentication

Automated Authentication Management

Automate authentication operations by combining multiple Plezi API endpoints. Agents can list contact fields and then create a contact in a single workflow.

Call GET /settings/contact_fields to list contact fields, then verify the result

AI Agent Integration via Jentic

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

Key Endpoints

13 endpoints — plezi is a marketing automation platform.

METHOD

PATH

DESCRIPTION

GET

Verify authentication

GET

/settings/contact_fields

List contact fields

POST

/contacts

Create a contact

GET

/contacts

List contacts

GET

/export_all_contacts

Export all contacts

GET

/contacts_updated

Get recently updated contacts

GET

/contacts_updated_by_score

Filter contacts by behavior score

GET

/subscriptions

Export subscriptions

GET

Verify authentication

GET

/settings/contact_fields

List contact fields

POST

/contacts

Create a contact

GET

/contacts

List contacts

GET

/export_all_contacts

Export all contacts

GET

/contacts_updated

Why Jentic?

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

Credential isolation

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

Time to first call

Direct Plezi 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 Plezi API through Jentic.

What authentication does the Plezi API use?

The Plezi 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 verify authentication with the Plezi API?

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

What are the rate limits for the Plezi 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 verify authentication through Jentic?

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

How many endpoints does the Plezi API have?

The Plezi API exposes 13 endpoints covering authentication, contact lists, contacts operations.

Plezi API

Connect the Plezi API to your agent

Capabilities

Start building with Plezi API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs