canonical: https://jentic.com/apis/placetel.de/placetel

# Placetel De Placetel API

--- Introduction <h2>Create custom integrations or automate your workflows with the Placetel REST API.</h2> To make a request to our API, you will need to specify an HTTP **method** and a **path**. Additionally, you can specify request **headers**, **query** and **body** parameters. The API will return the response status code, response headers, and dependening on status and resource a response bo. The API exposes 118 endpoints secured with apiKey authentication.

## For AI agents

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

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create an agent
- Fetch all call center agents
- Update an agent
- Pick a call center call

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create an agent', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Call_Center_Agents** — Operations for call_center_agents
- **Call_Center_Calls** — Operations for call_center_calls
- **Call_Center_Queues** — Operations for call_center_queues
- **Call_Detail_Records** — Operations for call_detail_records
- **Calls** — Operations for calls

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 64 / 100
  - Developer Experience & Jentic Compatibility: 60 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 79 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/placetel.de/placetel/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Placetel by hand means learning its Authorization header token auth and hand-building requests across its call-center agent, call and queue endpoints yourself. Through Jentic you install once, import Placetel from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Placetel puts the resource id in the URL path (`/call_center_agents/{id}`, `/call_center_queues/{id}`), so a rule can pin your agent to one agent or queue: it reads and updates that resource and nothing else. You choose the operations it may call, so state-changing ones like updating a queue are not included unless you add them.
- **Credential handling:** Your Placetel token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list call center agents' or 'pick up a queued call', and Jentic returns the matching Placetel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Placetel API?

Yes. Because you run Jentic One yourself, your own rules decide which Placetel operations and credentials the agent may use. Placetel puts the resource id in the URL path, such as `/call_center_agents/{id}` and `/call_center_queues/{id}`, so a rule can pin the agent to a single agent or queue and let it read and update only that resource. You also choose which operations are exposed, so state-changing calls like updating a queue stay out of reach unless you add them.