Authenticate API requests securely using your Opportunities API credentials (API key and OAuth2 as supported by your plan).
Rankr authenticates with the Opportunities API using a secure API key and OAuth2 flow. Store credentials securely and rotate keys regularly.
Core endpoints include: GET /opportunities/search, GET /opportunities/:id, GET /opportunities/pipelines, POST /opportunities, PUT /opportunities/:id, PUT /opportunities/:id/status, DELETE /opportunities/:id. These endpoints let you search, retrieve, create, update, and delete opportunities and manage statuses.
Trigger: when a new opportunity is created in Rankr.
Actions: create a corresponding opportunity in Opportunities API and attach sponsor data.
POST /opportunities
Key fields: id, name, email, pipeline_id, stage, close_date
Trigger: status changes in Opportunities or Rankr.
Actions: push status updates to the other system to keep data aligned.
PUT /opportunities/:id/status
Key fields: id, status, updated_at
Trigger: opportunity status becomes ‘won’ or ‘closed’.
Actions: create or attach an Accredible certificate to the Opportunity and push certificate data to Accredible.
POST /opportunities/:id/certificates
Key fields: id, certificate_id, applicant_email, certificate_status
Benefit 1: Automate end-to-end workflows without writing code.
Benefit 2: Real-time data synchronization across Rankr and Opportunities API.
Benefit 3: Clear insights through centralized logging and reporting.
Key elements include endpoints, authentication, field mapping, webhooks, and error handling. Processes cover setup, testing, mapping, and monitoring.
A potential customer who has shown interest and is tracked in Rankr.
A qualified lead that has moved into a potential deal and is tracked in the pipeline.
A sequence of stages representing the sales process.
A real-time notification sent to another system when an event occurs.
When a deal is marked won in Rankr, automatically generate and send an Accredible certificate.
Pull certificate status and issuance data back into Rankr for a complete profile.
Notify teams when a certificate is issued or revoked.
Obtain an API key and client credentials from the Opportunities API dashboard and configure OAuth2.
Map Rankr fields to Opportunities API fields and set up test calls.
Run test scenarios, monitor logs, and set alerts for failures.
Authentication is accomplished via an API key and OAuth2. Start by generating an API key in the Opportunities API dashboard and configure Rankr to include the key in request headers. For ongoing calls, rotate keys regularly and apply scoped tokens to limit access.
The primary endpoints are search, retrieve by ID, pipelines, create, update, and delete as listed above. Test calls in a sandbox environment before going live to ensure mappings and permissions are correct.
Yes. You can automate certificate issuance when an opportunity is won. Map certificate fields, trigger certificate creation on close, and attach the Accredible certificate data to the opportunity.
Yes—no-code automations are supported via Zapier or Rankr’s built-in workflows. These actions can call the API endpoints without writing code.
Map fields between Rankr and GHL using field keys, endpoints, and data types. Typical mappings include name, email, pipeline_id, stage, and status.
Data security is protected with TLS, API keys, and OAuth2. Follow best practices: least privilege, secret management, and access auditing.
API usage is tracked in the Opportunities API dashboard with rate limits. Set usage alerts and review logs to catch errors early.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
