Authenticate requests to the 46elks GHL API using an API key and secure signature. Store credentials securely in Rankr.
Rankr authenticates to GHL using API keys and tokens configured in the app settings.
Endpoint examples include: POST /sms/send, GET /messages/{id}/delivery, POST /contacts, POST /webhooks, GET /accounts. There are many more endpoints available through the 46elks API.
Trigger when a new lead is created in Rankr
Send SMS through 46elks and log the event in Rankr
POST /sms/send
Required: to, message, sender_id
Trigger when a contact status changes in Rankr
Update 46elks contact and trigger a webhook
PATCH /contacts/{id}
Required: id, status
Trigger when a message is sent in Rankr
Fetch delivery status from 46elks and store in Rankr
GET /messages/{id}/delivery
Required: id
Drag and drop workflow builder to orchestrate messaging
Instant automation without custom development
Faster time to value for campaigns
A quick glossary of terms used in this integration and how data flows between Rankr and the GHL API
Verifying identity and rights to access the GHL API and Rankr resources.
A callback URL that receives events from 46elks or Rankr when actions occur.
A specific URL path in the API used to perform a function such as sending a message.
The data sent with an API request or returned in a response.
Send a personalized SMS to a new lead when created in Rankr using 46elks.
Route messages by segment in Rankr to different 46elks endpoints.
Push status updates to customers via SMS or voice using 46elks.
Collect API keys from 46elks and client credentials from Rankr.
Enter keys in Rankr, set webhooks, and test permissions.
Run end-to-end tests, verify delivery, then activate the connection.
You do not need to write code to connect Rankr with 46elks via the GHL API. The no code builder in Rankr lets you configure triggers and actions and map fields between Rankr and 46elks. Use Rankr’s no-code workflow builder to configure SMS actions and automate messaging without coding. If you need more, you can extend workflows with custom scripts later.
Use API keys or tokens to authenticate calls to the GHL API and Rankr. Store credentials securely and rotate keys regularly. Webhook signing helps verify the source of events.
Essential endpoints typically include sending messages, checking delivery status, and managing contacts. Your setup may vary, but these endpoints cover common messaging workflows. Integrations often leverage a subset of the full API to keep the flow simple while preserving reliability.
Yes. Rankr provides a testing mode and sandbox credentials. Validate message formats, endpoints, and delivery receipts before going live. Use test data and monitor logs to confirm that triggers fire correctly and that delivery statuses update as expected.
Message quotas depend on your 46elks plan. In Rankr, you can set limits and monitor usage from the dashboard. Plan your campaigns with adequate buffer for peak periods to avoid interruptions.
API keys for 46elks are available in your 46elks account. Rankr will reference them in the integration settings. For Rankr, generate a client secret in the app settings. Keep keys secret and restrict their scope to the integration only.
Webhooks notify Rankr of events such as delivery reports. You can configure endpoints to receive and process these events in real time. Verify webhook signatures and retry logic to ensure reliable event handling.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
