Coria9404 1 Withdrawal Status Management API
Browse all Swaggerhub Coria9404 1 APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource Controlnone4 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically access Withdrawal Status Management API resources. Covers 4 operations.
Use for: I need to integrate with Withdrawal Status Management API, Find available withdrawal status management operations, Get the current status of Withdrawal Status Management API resources, List all records from Withdrawal Status Management API
Not supported: Does not handle payments, communications, or crm - use for withdrawal status management only.
An API to retrieve, add, edit, and delete withdrawal statuses. The API exposes 4 endpoints.
Install Jentic One Beta
Connect the Withdrawal Status Management API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Withdrawal Status Management 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.
1
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%2Fswaggerhub.coria9404-1%2Fapi-de-gestin-de-estados-de-retiro" | sh2
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%2Fswaggerhub.coria9404-1%2Fapi-de-gestin-de-estados-de-retiro" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Withdrawal Status Management API.
Access Withdrawal Status Management API resources via REST API
Manage withdrawal status data programmatically
Integrate Withdrawal Status Management API into automated workflows
Query and filter Withdrawal Status Management API records by parameters
Monitor Withdrawal Status Management API operational status and events
Use Cases
Patterns agents use Withdrawal Status Management API for, with concrete tasks.
★ Withdrawal Status Management Operations
Use the Withdrawal Status Management API to perform withdrawal status management operations programmatically. The API provides 4 endpoints covering core functionality including retrieving all withdrawal statuses, adding a new withdrawal status, editing a withdrawal status by ID.
Execute a primary operation against the Withdrawal Status Management API
Automated Withdrawal Status Workflows
Automate withdrawal status operations by combining multiple Withdrawal Status Management API endpoints. Agents can add a new withdrawal status and then edit a withdrawal status by ID in a single workflow.
Add a new withdrawal status and then update it via the Withdrawal Status Management API
AI Agent Integration via Jentic
AI agents discover and call Withdrawal Status Management 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 tokens manually.
Search Jentic for 'withdrawal status management API', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — an api to retrieve, add, edit, and delete withdrawal statuses.
METHOD
PATH
DESCRIPTION
GET
/est_retiro
Get all withdrawal statuses
POST
/est_retiroAgregar
Add a new withdrawal status
PUT
/est_retiroEditar/{est_retiroId}
Edit a withdrawal status by ID
DELETE
/est_retiroEliminar/{est_retiroId}
Delete a withdrawal status by ID
GET
/est_retiro
Get all withdrawal statuses
POST
/est_retiroAgregar
Add a new withdrawal status
PUT
/est_retiroEditar/{est_retiroId}
Edit a withdrawal status by ID
DELETE
/est_retiroEliminar/{est_retiroId}
Delete a withdrawal status by ID
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Withdrawal Status Management API by hand means pointing at its SwaggerHub mock host, matching the add, edit, and delete request formats, and parsing responses yourself even though it takes no auth. Through Jentic you install once, import the Withdrawal Status Management API from the API Directory, store any connection detail once, and your agent calls it.
Permission scoping
This API puts the withdrawal-status id in the URL path (/est_retiroEditar/{est_retiroId}), so a rule can pin your agent to reading withdrawal statuses: you choose the operations it may call, so writes like adding, editing, or deleting a status are not included unless you add them.
Credential isolation
Any Withdrawal Status Management API connection detail 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 'list withdrawal statuses' or 'add a withdrawal status', and Jentic returns the matching Withdrawal Status Management API 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
FAQs
Specific to using Withdrawal Status Management API through Jentic.
What authentication does the Withdrawal Status Management API use?
The Withdrawal Status Management API uses none authentication. 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.
What are the rate limits for the Withdrawal Status Management 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 use withdrawal status management API through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use withdrawal status management API'. Jentic returns the matching Withdrawal Status Management API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Withdrawal Status Management API have?
The Withdrawal Status Management API exposes 4 endpoints covering withdrawal statuses operations.
Does the Withdrawal Status Management API support pagination?
Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.
Can I limit what my agent is allowed to do with the Withdrawal Status Management API?
Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, so you can grant only reading all withdrawal statuses (GET /est_retiro) and withhold the write operations. That means adding a status (POST /est_retiroAgregar), editing one by ID (PUT /est_retiroEditar/{est_retiroId}), and deleting one by ID (DELETE /est_retiroEliminar/{est_retiroId}) stay off limits unless you explicitly allow them. You control the connection details the agent uses, so it can only reach the operations you have approved.
GET STARTED