canonical: https://jentic.com/apis/rest-demo.wannme.com/rest-demo-wannme

# Rest Demo Wannme WANNME API REST

Welcome to WANNME Integration API. The API exposes 133 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get debt case by iddebtcase with post (wannme id), get debt case by iddebtcase (wannme id). Covers 133 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get Debt case by idDebtcase with Post (WANNME id)
- Update existing Debt case by idDebtcase.
- Multi-criteria search of Debt cases
- Cancel Debt case by idDebtcase.
- Create new payment for a Debt case specified by idDebtcase.

## Use cases

### Developer Tools Operations

Use the WANNME API REST to perform developer tools operations programmatically. The API provides 133 endpoints covering core functionality including get debt case by iddebtcase with post (wannme id), get debt case by iddebtcase (wannme id), update existing debt case by iddebtcase..

Example prompt: Call POST `/wannmepay/debt-case/{idDebtcase}` to get debt case by iddebtcase with post (wannme id)

### Automated WANNME PAY MASTER DATA Management

Automate wannme pay master data operations by combining multiple WANNME API REST endpoints. Agents can get debt case by iddebtcase (wannme id) and then update existing debt case by iddebtcase. in a single workflow.

Example prompt: Call GET `/wannmepay/debt-case/{idDebtcase}` to get debt case by iddebtcase (wannme id), then verify the result

### AI Agent Integration via Jentic

AI agents discover and call WANNME API REST 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 'get debt case by iddebtcase with post (wannme id)', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/wannmepay/debt-case/{idDebtcase}` | Get Debt case by idDebtcase with Post (WANNME id) |
| GET | `/wannmepay/debt-case/{idDebtcase}` | Get Debt case by idDebtcase (WANNME id) |
| PUT | `/wannmepay/debt-case/{idDebtcase}` | Update existing Debt case by idDebtcase. |
| POST | `/wannmepay/debt-case/search` | Multi-criteria search of Debt cases |
| GET | `/wannmepay/debt-case/search` | Multi-criteria search of Debt cases |
| POST | `/wannmepay/debt-case/{idDebtcase}/action/cancel` | Cancel Debt case by idDebtcase. |
| POST | `/wannmepay/debt-case/{idDebtcase}/payment` | Create new payment for a Debt case specified by idDebtcase. |
| POST | `/wannmepay/debt-case/{idDebtcase}/payment/list` | List of payments of a Debt case specified by idDebtcase. |

## Key resources

- **WANNME PAY MASTER DATA** — Operations for Master data in WANNME PAY.
- **WANNME PAY DEBT CASES** — Operations for Debt cases payments in WANNME PAY
- **WANNME PAY RECURRENT PAYMENTS** — Operations for Recurrent payments in WANNME PAY
- **WANNME PAY PAYMENTS** — Operations for Payments in WANNME PAY
- **WANNME PAY MERGE PAYMENTS** — Operations for Merge payments in WANNME PAY

## Why Jentic

- **Setup:** Wiring the WANNME API REST by hand means passing your API key in the Authorization header, targeting the rest-demo.wannme.com/integration/v2 host, and managing debt-case flows yourself. Through Jentic you install once, import WANNME API REST from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** WANNME API REST puts the debt-case id in the URL path (`/wannmepay/debt-case/{idDebtcase}/...`), so a rule can pin your agent to one debt case: it can read and register payments for that case and nothing else. You choose the operations it may call, so actions like case cancellation are not included unless you add them.
- **Credential handling:** Your WANNME API REST key 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 'get a debt case by id' or 'register a payment on a debt case', and Jentic returns the matching WANNME API REST 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 WANNME API REST use?

The WANNME API REST 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 get debt case by iddebtcase with post (wannme id) with the WANNME API REST?

Yes. Use the POST `/wannmepay/debt-case/{idDebtcase}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the WANNME API REST?

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 get debt case by iddebtcase with post (wannme id) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get debt case by iddebtcase with post (wannme id)'. Jentic returns the matching WANNME API REST operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the WANNME API REST have?

The WANNME API REST exposes 133 endpoints covering wannme pay master data, wannme pay debt cases, wannme pay recurrent payments operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which WANNME API REST operations and credentials the agent may use. Because the API puts the debt-case id in the URL path, such as `/wannmepay/debt-case/{idDebtcase}`, you can pin the agent to a single debt case and let it only read that case and register payments on it. You choose the operations it may call, so actions like cancelling a debt case stay off-limits unless you explicitly allow them.