How to build your own Atendalia integration
A custom integration can receive Atendalia events through outgoing webhooks or use an API key to manage appointments. Define the direction of data, needed events and verification before writing code.
What you can do with your own system
Send appointments and alerts to the software your business already uses. A webhook is an automatic notification; an API lets your system ask for information or an action. You can avoid Zapier when your system can receive data directly. Your technical team prepares that connection. If you only need a calendar, start with Atendalia’s calendar or the direct Google Calendar connection.
Choose the direction of data
Use an outgoing webhook when your system needs a notification about an appointment event. Atendalia sends it to your HTTPS endpoint. Use the public API when your application needs to inspect availability or manage bookings.
The connections are not automatically bidirectional. Decide which system owns each record to avoid duplicate bookings.
Prepare a secure endpoint
A custom webhook needs a public HTTPS URL. The dashboard rejects private and local addresses. Store the signing secret on your server and validate requests before handling customer or booking information.
Return predictable responses and log errors without unnecessary personal data. Start with fictitious test records.
- Use HTTPS on a domain you control.
- Subscribe only to events your workflow needs.
- Protect and rotate exposed secrets.
- Handle repeated events safely.
Configure and test in the dashboard
Open Integrations, select My own system, enter the URL and secret, then choose events. Run a test and inspect both the integration history and your server logs.
For workflows without a maintained endpoint, consider Zapier or Make and check their separate pricing and limits.
Use the API for the right workflows
An API key is shown only once. Keep it on the server, never in public JavaScript or an unprotected mobile app. Revoke keys you no longer use.
The public API provides appointment and availability routes. Review fields, responses and errors before automating synchronization, then test creation and cancellation with sample data.
Verify the complete journey
Create a test booking, confirm the expected event arrived, inspect fields received by your system and make sure no second booking appeared. Repeat with a cancellation and a failed endpoint response.
The My own system integration guide contains an example payload and the available events. Use it as your reference before handling real customers.