yourang.ai Logo
Back to the platform
Documentation
Get started
  • What the platform is
  • First access
  • Platform overview
  • Quick glossary
Dashboard Assistant
  • What the dashboard assistant is
  • How to use it
  • What it can do
  • Safety and privacy
  • Plans and usage limits
Voice agent
  • Basic configuration
  • Voices and language
  • Instructions
  • Prompt tokens
  • Advanced settings
  • Evaluation criteria
  • Testing and playground
  • Updating instructions
  • External Tools
  • Built-in tools
  • MCP servers
Models offered
  • What models are and why they matter
  • Voice models
  • AI models
  • Choosing the right combination
Documents and knowledge base
  • What the knowledge base is
  • Uploading and managing documents
  • How search works during a call
  • Best practices
Calls
  • Call history
  • Transcripts and summaries
  • Audio recordings
  • Filters and search
  • Data export
Call transfers
  • When and why to transfer a call
  • Departments
  • System tools
  • AI after-hours
  • Routing rules
  • Operator app (iOS / Android)
WhatsApp
  • WhatsApp Business in yourang.ai
  • Real-time chat
  • Automations
  • Approved templates
  • WhatsApp contacts and lists
  • WhatsApp AI agents
Actions and campaigns
  • What actions are
  • SMS campaigns
  • Email campaigns
  • Scheduling and batch sends
Reservations
  • Calendar view
  • Availability rules
  • Confirmations and reminders
  • Changes and cancellations
Contacts
  • Customer directory
  • CSV import
  • Lists and segments
  • Custom fields
Shop and catalogue
  • The shop in yourang.ai
  • Product and service catalogue
  • Order management
  • OCR and price-list import
Integrations
  • Connect Apple Calendar
  • Connect HubSpot
  • Integrations overview
  • Calendar
  • WhatsApp
  • SMS and email
  • Business software and PMS
  • Outbound webhooks
Workflows
  • What workflows are
  • Nodes and blocks
  • Triggers and webhooks
  • Practical examples
Call center and dialer
  • What the yourang.ai call center does
  • Outbound campaigns
  • Human operators
  • Contact lists and live sync
  • Operator panel
External APIs and developers
  • yourang.ai for developers
  • API keys and authentication
  • Main endpoints
  • Incoming webhooks
Use cases
  • Hotels and accommodation
  • Restaurant
  • B&Bs and short-term rentals
  • Beauty center and spa
  • Travel agency
Pricing and plans
  • How pricing works
  • Subscription plans
  • Wallet and credits
  • Consumption and invoices
  • Changing, suspending, or cancelling the plan
Management
  • Account and organization
  • Billing and subscription
  • Team and roles
  • Security and privacy
  • Notifications
Business information
  • Business details
  • Location and address
  • Opening hours
  • AI assistant hours
  • Departments and team
Resources
  • Frequently asked questions
  • Complete glossary
  • Support
Documentation›External APIs and developers›yourang.ai for developers

External APIs and developers

yourang.ai for developers

What the external API offers, who it is for, general principles.

For management systems, portals, custom applications, or advanced automations, yourang.ai exposes a REST API and a webhook system that let you read and write data and receive real-time notifications.

Who it's for

  • Internal developers. IT teams who want to integrate yourang.ai with a PMS, a management system, a mobile app.
  • Integration partners. Software houses building solutions for hospitality or services who want to offer a yourang.ai connection to their customers.
  • Power users with technical skills. Those who use no-code tools (Zapier, Make, n8n) can leverage APIs and webhooks without writing traditional code.

Technical principles

  • REST + JSON. Standard conventions: GET, POST, PUT, DELETE on readable URLs. All exchanges are in JSON UTF-8.
  • URL versioning. The API has a version prefix (e.g. /api/external/v1/). Breaking changes go into new versions; old ones remain supported with announced deprecation periods.
  • Separate schema. External API payloads do not share internal product fields: you have a stable surface, independent of internal evolutions.
  • HTTPS required. All calls happen over TLS. No plaintext endpoints.

Complete technical documentation

This section explains the main concepts and use cases. For the technical details of each endpoint (parameters, responses, error codes), there is a separate OpenAPI documentation, accessible from the developer panel.

Was this page helpful?

PreviousOperator panelNextAPI keys and authentication