External APIs and developers
Main endpoints
Overview of API areas and the most common use cases.
The API is organized by resources, each with its own endpoints. Here's a map of the main areas.
Quick start
Three ready-to-use snippets to call the external API. Replace `yr_live_xxx` with your personal key (see the “API keys and authentication” page).
list-contacts.sh · bash
curl -X GET "https://api.yourang.ai.io/external/v1/contacts?limit=20" \
-H "Authorization: Bearer yr_live_xxx" \
-H "Accept: application/json"API areas
- Contacts. Read, create, update CRM contacts. Two-way synchronizations with management systems, periodic imports from external sources.
- Calls. Retrieve call history with metadata, transcripts, summaries. Trigger outbound calls programmatically.
- Reservations. Create, read, modify reservations. Sync the yourang.ai calendar with the PMS or management system.
- Orders. For the Shop module: create orders from external systems, read status, receive payment confirmations.
- Documents. Upload and manage the knowledge base via API. Useful for those who keep the catalog/price list in a source system and want to replicate it in yourang.ai.
- Webhooks. Configure the URLs to which yourang.ai notifies events (see dedicated page).
Typical use cases
- Sync management system -> yourang.ai. Every night the PMS publishes new contacts and the day's reservations to yourang.ai. The voice assistant works with always-aligned data.
- yourang.ai -> management system. When the assistant records a new reservation, it reports it to the main management system via API. The assistant becomes an input channel to the central system.
- Custom dashboard. A BI or Excel sheet connected to the API shows custom aggregated data, beyond the standard panel.
- Automations with n8n / Make. No-code workflows that react to yourang.ai events to orchestrate actions in other systems: Slack, Notion, Airtable.
Pagination and filters
All list endpoints support pagination (limit + offset) and filters on the main fields. For bulk exports it's better to paginate with reasonable sizes (50-100 per page) rather than asking for everything at once: avoids timeouts and load on systems.
Was this page helpful?