Authenticate to the Opportunities API with your GHL credentials and ensure the scope opportunities.readonly is granted.
Use your 17hats OAuth credentials or API key to authorize requests to the Opportunities API and keep credentials secure.
Key endpoints include GET /opportunities/search, GET /opportunities/:id, GET /opportunities/pipelines, POST /opportunities, PUT /opportunities/:id, PUT /opportunities/:id/status, DELETE /opportunities/:id, PUT /opportunities
Trigger: A new lead is created in 17hats triggers a new Opportunity in the Opportunities API.
Actions: Map lead fields to Opportunity fields such as name, amount, close date and pipeline, then POST /opportunities.
Method Path: POST /opportunities
Key Fields: lead_id, name, amount, pipeline_id
Trigger: Changes to an opportunity in 17hats trigger an update in the Opportunities API
Actions: Update fields such as status and amount using PUT /opportunities/:id after mapping from 17hats
Method Path: PUT /opportunities/:id
Key Fields: id, status, amount, close_date
Trigger: Schedule or manual pull to fetch opportunities into 17hats
Actions: Use GET /opportunities/search and GET /opportunities/:id to retrieve data and map back to 17hats
Method Path: GET /opportunities/search
Key Fields: query, id
Benefit 1: Fast no code automation between 17hats and the Opportunities API
Benefit 2: Centralized data with automatic field mapping
Benefit 3: Real time sync to keep opportunities up to date
Elements and processes include endpoints authentication data mapping and error handling to support a smooth integration
Definition: Verifying identity and granting access to data via tokens or keys
Definition: A URL in the API used to perform actions such as search get or update
Definition: An open standard for access tokens used to authorize API requests
Definition: Permissions granted to an integration for example readonly
Automatically create an Opportunity in the API when a new lead is added in 17hats
Sync stage updates from 17hats into the Opportunities API to keep pipelines aligned
Pull opportunity data from the API back into 17hats to avoid manual entry
Obtain OAuth tokens or API keys and grant the scope opportunities.readonly
Create a field mapping between 17hats fields and Opportunities API fields such as name amount and pipeline_id
Run tests verify data flows and enable live syncing with monitoring
The Opportunities API lets you search retrieve create and update opportunities from 17hats. You can query pipelines fetch by id and inspect stages to drive automation. This helps standardize data and speed up sales workflows.
Usually you do not need a separate developer account if your integration platform handles OAuth or API keys. Some platforms provide built in connectors that simplify setup. You will still need valid credentials from 17hats and the correct permissions.
Authenticate with OAuth 2.0 tokens or API keys and request the scope opportunities.readonly. Store tokens securely and rotate credentials regularly.
To create a new opportunity use the endpoint POST /opportunities. Map required fields such as name, amount and pipeline_id. On success you receive an opportunity id.
Yes, you can enable real time or scheduled sync. Changes in 17hats can trigger updates in the Opportunities API, allowing continuous data alignment.
If an endpoint returns an error review the HTTP status code and message. Check authentication, payload structure and required fields. Implement retries with backoff.
Rate limits vary by plan. Check your account or API docs for quotas. If you hit limits, throttle requests or upgrade, and optimize field mappings to reduce calls.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
