canonical: https://jentic.com/apis/swaggerhub.sura-panama/assistance-api

# Sura Panama Assistance API

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.

## For AI agents

Programmatically cargar las asistencias viales, ping endpoint. Covers 3 operations with apiKey authentication.

## Scope

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

## Capabilities

- 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

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

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

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

Example prompt: Search Jentic for 'cargar las asistencias viales', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Assistance Api** — Operations for assistance api

## Why Jentic

- **Setup:** Wiring the Assistance API by hand means setting its X-API-KEY header, targeting the assistance host, and handling the create and health-check calls and retries yourself. Through Jentic you install once, import the Assistance API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Assistance API takes its target in the request body rather than the URL path, so scope the agent to the operations it needs, such as posting a mobility assistance or running the ping check. You choose which operations it may call, so anything you leave out stays unavailable to the agent.
- **Credential handling:** Your Assistance API 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 'submit a roadside assistance record' or 'check service health', and Jentic returns the matching Assistance API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

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

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

Yes. Jentic One is self-hosted, so your own rules decide which Assistance API operations and credentials the agent may use. You can allow only the calls it needs, such as posting a mobility assistance record via POST /assistance-api/api/movilidad/assistances or running the GET ping and health-check endpoints, and leave the rest unavailable. Because the API takes its target in the request body rather than the URL path, scoping happens at the operation level, and any operation you do not grant stays out of the agent's reach.