Sura Panama Assistance API
Browse all Swaggerhub Sura Panama APIs★ Only Publicly Available OpenAPI DocumentAnalyticsWeb AnalyticsapiKey3 EndpointsREST
For Agents
Programmatically cargar las asistencias viales, ping endpoint. Covers 3 operations with apiKey authentication.
Use for: I need to cargar las asistencias viales, I want to ping endpoint, Search for health check endpoint, List all records from Assistance API
Not supported: Does not handle payments, communications, or crm — use for analytics only.
Permite gestionar la trazabilidad de las distintas asistencias que son reportados por los Proveedor asociados a estas acciones. Pueden ser de distintos tipos p.ej. asistencia-vial para siniestros, asistencia en el hogar, asistencia juridica etc. The API exposes 3 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Assistance API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Assistance 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Assistance API.
Cargar las Asistencias Viales
Ping endpoint
Health check endpoint
Query and filter Assistance API records by parameters
Monitor Assistance API operational status and events
Use Cases
Patterns agents use Assistance API for, with concrete tasks.
★ Analytics Operations
Use the Assistance API to perform analytics operations programmatically. The API provides 3 endpoints covering core functionality including cargar las asistencias viales, ping endpoint, health check endpoint.
Call POST /assistance-api/api/movilidad/assistances to cargar las asistencias viales
Automated Assistance Api Management
Automate assistance api operations by combining multiple Assistance API endpoints. Agents can ping endpoint and then health check endpoint in a single workflow.
Call GET /assistance-api/api/assistances/ping to ping endpoint, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Assistance 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 'cargar las asistencias viales', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
3 endpoints — permite gestionar la trazabilidad de las distintas asistencias que son reportados por los proveedor asociados a estas acciones.
METHOD
PATH
DESCRIPTION
POST
/assistance-api/api/movilidad/assistances
Cargar las Asistencias Viales
GET
/assistance-api/api/assistances/ping
Ping endpoint
GET
/assistance-api/api/assistances/health-check
Health check endpoint
POST
/assistance-api/api/movilidad/assistances
Cargar las Asistencias Viales
GET
/assistance-api/api/assistances/ping
Ping endpoint
GET
/assistance-api/api/assistances/health-check
Health check endpoint
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Assistance 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., 'cargar las asistencias viales') and Jentic returns the matching Assistance API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Assistance 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.
FAQs
Specific to using Assistance API through Jentic.
What authentication does the Assistance API use?
The Assistance API uses an API key passed in the `X-API-KEY` 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 cargar las asistencias viales with the Assistance API?
Yes. Use the POST /assistance-api/api/movilidad/assistances endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Assistance 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 cargar las asistencias viales through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'cargar las asistencias viales'. Jentic returns the matching Assistance API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Assistance API have?
The Assistance API exposes 3 endpoints covering assistance api operations.
GET STARTED