A centralized repository designed for advanced integrations. Explore endpoints, test webhooks, and utilize our toolkits to build robust connections.
Technical Scope
Landing page for Alleviate. Links to Setup and Send to Alleviate tools. POST to /api/alleviate/send to submit patient/lead data.
Practical Use Case
Use this page to access Alleviate API tools. Configure credentials in Setup, then send patient data via the Send endpoint.
Technical Scope
Configure API settings, credentials, and field mappings for the Alleviate API. Generate GHL-ready request bodies.
Practical Use Case
Use this page to configure your Alleviate API integration, including API keys and field mappings.
Technical Scope
POST to /api/alleviate/send. Accepts email, first_name, last_name, phone, date_of_birth, and other contact fields. Forwards to Alleviate when configured.
Practical Use Case
Send patient/lead data directly to Alleviate. Use the payload structure from Setup or the examples on the Send page.
Technical Scope
Configure API settings, form codes, account IDs, field mappings, and question mappings for the CRIO API. Generate request bodies with proper formatting.
Practical Use Case
Use this page to configure your CRIO API integration, including API keys, field mappings, and question configurations. Generate properly formatted request bodies.
Technical Scope
Direct endpoint to send patient data to CRIO API. Automatically handles DOB formatting (MM/DD/YYYY → DD-MMM-YYYY), sex formatting (Male/Female → MALE/FEMALE), and phone formatting to XXX-XXX-XXXX. Supports sandbox and production environments (US, Canada, Australia, Europe).
Practical Use Case
Use this endpoint to send patient data directly to CRIO. The API handles all formatting automatically, so you don't need code nodes for date, phone, or gender conversion.
Technical Scope
ToolKit provides utilities for working with the CRIO API, including sites and studies management. Query available sites and studies using API credentials.
Practical Use Case
Use this tool to explore available sites and studies for the CRIO API integration. Get site IDs and study information needed for patient submissions.
Technical Scope
Landing page for Objective Health. Links to Send to Objective Health tool.
Practical Use Case
Use this page to access Objective Health API tools and documentation.
Technical Scope
Step-by-step wizard: configure API key, study_id, site_id, field mappings (GHL variables), and prescreen questions. Outputs GHL-ready JSON and standard example body to copy.
Practical Use Case
Use this to build the exact request body you need - map contact fields and questions, then copy the generated JSON for your webhook or API call.
Technical Scope
POST to /api/objective-health/send-patient. Normalizes phone (digits only), DOB (YYYY-MM-DD), maps race to Objective Health values, maps recruitment_status (Qualified for Screening/Not Contacted → Referral, DNQ → Not eligible). Forwards to https://api.screen.objective.health/api/vip/patients with x-api-key.
Practical Use Case
Send study_id, site_id, API key, and contact fields. Use questions array or question_1/answer_1 style. Phone and DOB can be in any format; we convert. Race and recruitment_status are mapped automatically.
Technical Scope
Orchestrates a complete flow: retrieves API key, checks email existence, formats data, sends to RT V1 API, and optionally sends comments. Automatically chains all steps in sequence.
Practical Use Case
Use this endpoint when you have lead data ready to send and don't need to collect prescreen information first. Ideal for direct lead submissions from forms or CRM systems.
Technical Scope
Similar orchestration flow as no-prescreen but includes prescreen question handling. Validates and processes prescreen responses before sending lead data to RT V1 API.
Practical Use Case
Use this endpoint when you need to collect and validate prescreen information from leads before submission. Perfect for qualification workflows that require additional data collection.
Technical Scope
ToolKit provides utilities and tools for working with the Realtime API, including interview questions, referral sources, sites, and studies management.
Practical Use Case
Use this tool to explore available interview questions, referral sources, sites, and studies for the Realtime API integration.
Technical Scope
Configure API settings, credentials, and mappings for the Realtime API integration. Set up field mappings and question configurations.
Practical Use Case
Use this page to configure your Realtime API integration settings, including API keys, field mappings, and question configurations.
Technical Scope
Accepts full Advicemedia payload structure (form_code, account_id, location_id, source_url, campaign_name, contact fields, and question/answer pairs 1-25) and forwards it directly to Advicemedia API. Supports both full payload format and legacy nested contact format.
Practical Use Case
Use this endpoint to send lead data to Advicemedia. Configure GHL variables and questions using the Setup tool. Send the complete payload structure and the API will forward it to Advicemedia with proper authentication.
Technical Scope
Configure API settings, form codes, account IDs, location IDs, field mappings, and question mappings (1-15) for the SCR API. Generate GHL-formatted request bodies.
Practical Use Case
Use this page to configure your SCR API integration, including API keys, form codes, GHL variable mappings, and question configurations. Lock in your configuration to generate request body examples.
Technical Scope
Proxies Advicemedia PatientsVIP submissions endpoints (list + single/batch updates) using your bearer token and required privileges.
Practical Use Case
List submissions with filters/pagination, and update fields on a single submission or up to 100 submissions in one request.
Technical Scope
Direct endpoint to send lead data to Advicemedia API. Accepts the full payload structure and forwards it to Advicemedia with proper authentication headers.
Practical Use Case
Use this endpoint to send lead data directly to Advicemedia. Send the complete payload structure configured in the Setup tool.
Technical Scope
Same as SCR. When SCR_SANDBOX_BOUNCE_MODE=true, the endpoint returns the prepared payload without forwarding to Advicemedia. When false, operates identically to SCR.
Practical Use Case
Use for testing: point webhooks here and toggle bounce mode to verify payloads without sending real leads to Advicemedia.
Technical Scope
Same configuration wizard as SCR Setup. Generate request bodies for the SCR Sandbox endpoint.
Practical Use Case
Configure your SCR Sandbox integration. Use the same payload structure as SCR.
Technical Scope
POST /api/scr-sandbox/send-to-advicemedia. When bounce mode is ON, returns the prepared payload. When OFF, forwards to Advicemedia.
Practical Use Case
Test your lead payloads. With bounce mode ON, you'll see exactly what would be sent without actually sending.
Technical Scope
Configure all fields and generate the JSON payload for Study Team referrals. Set up API credentials, field mappings, and generate properly formatted request bodies.
Practical Use Case
Use this page to build your POST request body for Study Team referrals. Configure all required fields and generate the JSON payload ready to send.
Technical Scope
ToolKit provides utilities for working with the Study Team API, including sites and trials management. Query available referral sites and get trial IDs and site information.
Practical Use Case
Use this tool to explore available referral sites and trials. Get trial IDs and site information needed for Study Team referrals.