Rest Demo Wannme WANNME API REST

Name: WANNME API REST API
Brand: WANNME API REST
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey133 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the WANNME API REST to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WANNME API REST, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Frest-demo.wannme.com%2Frest-demo-wannme" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frest-demo.wannme.com%2Frest-demo-wannme" | 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 WANNME API REST API.

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.

GET STARTED

Start building with WANNME API REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use WANNME API REST API for, with concrete tasks.

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

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.

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.

Search Jentic for 'get debt case by iddebtcase with post (wannme id)', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

133 endpoints — welcome to wannme integration api.

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.

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

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 WANNME API REST API through Jentic.

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.