Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.visitoai.com/llms.txt

Use this file to discover all available pages before exploring further.

This page shows how to use coding assistants to work with the Visito API faster and more reliably.

​
What You Can Automate

  • Generate API clients and request helpers.
  • Build message and conversation workflows.
  • Add payment reconciliation scripts.
  • Run CRM-focused lead triage and template follow-up flows.
  • Keep openapi.json and docs in sync with backend routes.
  1. Keep your API key in environment variables.
  2. Share your openapi.json with the assistant context.
  3. Ask for tenant-safe patterns (company-scoped queries only).
  4. Ask the assistant to validate against real responses from sandbox data.

​
Common Prompt Template

You are integrating Visito API in <stack>.
Base URL: https://api.visitoai.com/v1
Auth: Authorization: Bearer $VISITO_API_KEY

Build:
1) list conversations
2) fetch conversation messages
3) send a plain text message
4) list payments with transfer details

Requirements:
- retry on 429/5xx with backoff
- typed response models
- structured error handling
- no client-side key exposure

​
CRM Playbook (All LLMs)

Use this flow for CRM triage and outreach:
  1. GET /conversations?limit=50&sortBy=updatedAt
  2. Score by summary + intent
  3. GET /conversations/{id}/actions for top conversations
  4. Check unresolved/manual/help actions
  5. GET /whatsapp-templates/{channelId}
  6. POST /whatsapp-templates/{channelId}/send

​
Codex Prompt

Implement a CRM automation flow with Visito API.

Step 1
- GET /conversations?limit=50
- use summary + intent for lead ranking

Step 2
- GET /conversations/{id}/actions
- skip contacts with unresolved critical actions

Step 3
- GET /whatsapp-templates/{channelId}
- map template by intent

Step 4
- POST /whatsapp-templates/{channelId}/send
- generate send log (CSV + JSON)

Requirements:
- retries for 429/5xx
- idempotency guard for duplicate sends
- typed DTOs and error mapper

​
Claude Code Prompt

Create a backend CRM orchestrator using Visito API.

Endpoints:
- GET /conversations
- GET /conversations/{id}/actions
- GET /whatsapp-templates/{channelId}
- POST /whatsapp-templates/{channelId}/send

Output:
- ranked conversations (high/medium/low)
- chosen template per conversation
- execution log with status and errors

Engineering constraints:
- runtime response validation
- strict error classes
- retry/backoff policy
- server-side API key only

​
Other LLMs Prompt

You are building CRM outreach automation with Visito API.
Use:
1) GET /conversations
2) GET /conversations/{id}/actions
3) GET /whatsapp-templates/{channelId}
4) POST /whatsapp-templates/{channelId}/send

Deliver:
- priority report
- template selection
- send result log

​
Safety Checklist

  • Never expose VISITO_API_KEY in frontend code.
  • Always send Authorization: Bearer <API_KEY>.
  • Keep conversation/action queries tenant-scoped.
  • Add idempotency logic before sending templates.