Placetel De Placetel API

Name: Placetel API
Brand: Placetel API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey118 EndpointsREST

For Agents

Programmatically create an agent, fetch all call center agents. Covers 118 operations with apiKey authentication.

Install Jentic One Beta

Connect the Placetel API to your agent

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

Create an agent

Fetch all call center agents

Update an agent

Pick a call center call

GET STARTED

Start building with Placetel API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Placetel API for, with concrete tasks.

★ Developer Tools Operations

Use the Placetel API to perform developer tools operations programmatically. The API provides 118 endpoints covering core functionality including create an agent, fetch all call center agents, update an agent.

Call POST /call_center_agents to create an agent

Automated Call_Center_Agents Management

Automate call_center_agents operations by combining multiple Placetel API endpoints. Agents can fetch all call center agents and then update an agent in a single workflow.

Call GET /call_center_agents to fetch all call center agents, then verify the result

AI Agent Integration via Jentic

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

Key Endpoints

118 endpoints — --- introduction <h2>create custom integrations or automate your workflows with the placetel rest api.

METHOD

PATH

DESCRIPTION

POST

/call_center_agents

Create an agent

GET

/call_center_agents

Fetch all call center agents

PUT

/call_center_agents/{id}

Update an agent

GET

/call_center_calls

Fetch all call center calls

POST

/call_center_calls/{id}/{pick}

Pick a call center call

POST

/call_center_queues

Create a queue

GET

/call_center_queues

Fetch all call center queues

PUT

/call_center_queues/{id}

Update a queue

POST

/call_center_agents

Create an agent

GET

/call_center_agents

Fetch all call center agents

PUT

/call_center_agents/{id}

Update an agent

GET

/call_center_calls

Fetch all call center calls

POST

/call_center_calls/{id}/{pick}

Pick a call center call

Why Jentic?

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

Credential isolation

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

Time to first call

Direct Placetel 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

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Placetel API through Jentic.

What authentication does the Placetel API use?

The Placetel 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 create an agent with the Placetel API?

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

What are the rate limits for the Placetel 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 an agent through Jentic?

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

How many endpoints does the Placetel API have?

The Placetel API exposes 118 endpoints covering call_center_agents, call_center_calls, call_center_queues operations.