Generate an API key with the scope funnels/redirect.readonly and attach it to Rankr to enable read access to redirects, pages, and funnel data in GHL.
In Rankr, securely store and apply the API key to establish a connection to Funnels API so you can read redirects and funnel information.
– GET /funnels/lookup/redirect/list; – funnels/redirect.write; – POST /funnels/lookup/redirect; – funnels/page.readonly; – GET /funnels/page; – funnels/funnel.readonly; – GET /funnels/funnel/list; – GET /funnels/pagecount.readonly; – GET /funnels/page/count; – DELETE /funnels/lookup/redirect/:id; – PATCH /funnels/lookup/redirect/:id; (Endpoints 13–17 are not used on this page).
Trigger when a user action occurs, then fetch redirect data with GET /funnels/lookup/redirect/list to route visitors to the correct URL.
Actions: create or update redirects with POST /funnels/lookup/redirect and PATCH /funnels/lookup/redirect/:id as needed.
Method path: /funnels/lookup/redirect
Key fields: id, source_funnel, destination_url, status
Trigger page retrieval with GET /funnels/page to list pages, monitor counts with GET /funnels/pagecount.readonly.
Actions: list pages via GET /funnels/page and retrieve counts via GET /funnels/pagecount.readonly.
Method path: /funnels/page
Key fields: page_id, funnel_id, page_count
Trigger: enumerate funnels via GET /funnels/funnel/list to populate your dashboard.
Actions: fetch funnel details via GET /funnels/funnel/list to drive analytics and reporting.
Method path: /funnels/funnel/list
Key fields: funnel_id, name, status
Build automated redirects and funnel flows without writing code.
Access endpoints directly from Rankr to create, read, update, and monitor funnels and pages.
Fast setup with clearly defined scopes and straightforward authentication.
Key elements include API, endpoints, triggers, and actions. This guide outlines how they work together to connect Funnels API with Rankr, including authentication, data flow, and typical use cases.
Definition: A defined set of endpoints, methods, and data formats that let Rankr interact with Funnels API.
Definition: A specific URL path that performs an action in Funnels API.
Definition: Events or conditions that initiate API calls from Rankr to Funnels API.
Definition: A secure authorization framework that grants Rankr access to Funnels API without exposing credentials.
Idea: When a user completes a step, use redirect lookup to route to the right page without manual setup.
Idea: Sync page views and counts back to Rankr dashboards via the Funnels API endpoints.
Idea: Route visitors to personalized pages using redirect rules and endpoints to fetch data.
Generate an API key or OAuth token with scope funnels/redirect.readonly for safe access, and attach to the Rankr workspace.
Authorize Rankr to access Funnels API and run a test call to GET /funnels/lookup/redirect/list to verify redirects.
Create redirects, pages, and funnel mappings using the available endpoints to automate redirects.
Yes. The Funnels API + Rankr integration is designed for no-code setup, so you can connect, configure, and automate redirects without writing code. For advanced automations, you can extend with custom steps while still benefiting from prebuilt endpoints and scoped access.
Key endpoints for 97Display include GET /funnels/lookup/redirect/list to view redirects, POST /funnels/lookup/redirect and PATCH /funnels/lookup/redirect/:id to create or update redirects, GET /funnels/page to fetch pages, and GET /funnels/funnel/list to enumerate funnels.
Authenticate with an API key that uses the funnels/redirect.readonly scope. Store securely in Rankr and rotate keys as needed. For more control, consider OAuth tokens tied to a specific Rankr user account.
Yes. Use a staging environment or sandbox calls to verify behavior before touching live funnels. Begin with read-only endpoints to validate data flow and permissions.
Funnels API provides access to redirects, pages, and funnel metadata. You can read redirects, list and count pages, and enumerate funnels for dashboards and reports.
Common issues include missing permissions, invalid IDs, and environment mismatches. Validate scopes, try read-only endpoints first, and check for correct environment URLs.
Find more learning resources in Rankr’s knowledge base, the Funnels API reference, and the dedicated onboarding guides. Contact support for tailored assistance.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
