Integration Guides & APIs

The Expert-Led AIVRA Integration Process

Unlike self-service platforms, all major integrations and connections between AIVRA and your core business systems (CRMs, ERPs, databases) are performed by our certified integration experts.

This guarantees robust, secure, and performant data flow tailored specifically to your operational needs. Our team handles the authentication, schema mapping, and deployment of secure integration endpoints.

Our 4-Step Integration Workflow:

1. Discovery & Planning: Our expert meets with your team to define data points and workflow triggers.
2. Credential Handover: You securely provide our expert with necessary, least-privilege API keys/access credentials.
3. Build & Testing: Our expert builds and tests the secure connection in a staging environment.
4. Deployment & Handoff: The connection is deployed to production, and documentation is provided to your technical team.

AIVRA Public API Endpoints and Documentation Access

While primary integration is expert-led, we provide a robust RESTful API for advanced users and developers to monitor and trigger automations programmatically.

API Documentation:

• Base URL: `https://api.aivra.com/v1/`
• Authentication: All calls require a valid API key passed in the `Authorization: Bearer` header.
• Key Endpoints: `GET /workflows`, `POST /workflows/{id}/run`, `GET /logs/{workflowId}`.
• External Documentation: For comprehensive, interactive documentation, visit our developer portal: [Developer.AIVRA.com/docs/api](javascript:void(0);) (Placeholder link).

Required Credentials for CRM, ERP, and Database Integrations

To prepare for the expert-led integration session, ensure you have the necessary administrative credentials ready. We require these to set up secure, permanent access for the automation workflows.

Credential Checklist:

• Salesforce/HubSpot (CRM): User ID, Security Token, and Consumer Key/Secret (for OAuth 2.0).
• SAP/Oracle (ERP): Dedicated API user account with restricted read/write permissions for relevant modules.
• SQL Databases (Postgres, MSSQL): Dedicated read/write credentials for the specific tables/schemas required by the automation. Never provide root/admin database access.

Troubleshooting Existing Integration Failures and Errors

If an existing, expert-configured integration suddenly fails, review the following common causes before submitting a support ticket.

Checklist for Failures:

1. API Key Expiration: Check if the API key used by the workflow has been expired or regenerated in the source system.
2. Source System Change: Verify that no recent changes were made to the connected system's fields, endpoints, or network rules.
3. Rate Limiting: Check the integration logs for HTTP 429 errors, indicating the source system is limiting AIVRA's request volume.
4. Firewall/IP Restriction: Ensure that AIVRA's current egress IP range (available in the Admin Panel) is still whitelisted on your internal network.

Understanding Custom Connectors vs. Standard API Integrations

AIVRA distinguishes between standard connections using existing APIs and building completely custom connectors for legacy or proprietary systems.

Connector Types:

• Standard API Integration: Used for systems with well-documented APIs (e.g., Salesforce, Azure). Integration is performed by AIVRA experts during onboarding.
• Custom Connector Development: Required for systems that use older protocols, lack modern APIs, or are highly customized internal applications. This requires a separate Scope of Work (SOW) and specialized development resources.