🐛 Describe the Bug
The docs for GET Opportunity say that a notes array will be included with the response, but no such array is included in the response.
📍 API Endpoint
/opportunities/:id
✅ Expected Behavior
Notes associated with the Opportunity should be included in the response as the documentation specifies; or the documentation should be changed to reflect the actual API response.
💻 Screenshots or Code Samples
curl -L 'https://services.leadconnectorhq.com/opportunities/<opportunity_id>' \
-H 'Accept: application/json' \
-H 'Version: v3' \
-H 'Authorization: Bearer <my-bearer-token>' | jq
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 973 100 973 0 0 5740 0 --:--:-- --:--:-- --:--:-- 5757
{
"opportunity": {
"id": "PxSlfYH0jrTWDyPGcSBf",
"name": "GHL Test 6",
"monetaryValue": 0,
"pipelineId": "GbkXdmJw023wjgiPsUNH",
"pipelineStageId": "047383b5-4054-4c72-9bd6-bb34d8ba823b",
"status": "won",
"lastStatusChangeAt": "2026-04-14T16:59:12.771Z",
"lastStageChangeAt": "2026-05-08T06:03:36.595Z",
"createdAt": "2026-04-14T03:07:53.314Z",
"updatedAt": "2026-05-08T06:03:36.608Z",
"contactId": "MOsU2dtyy4kersU2CTdV",
"isAttribute": false,
"internalSource": {
"type": "CREATED",
"id": "69cdd5cb22015948f12dc8e1-mngvs024",
"apiVersion": "2021-07-28",
"channel": "OAUTH",
"source": "INTEGRATION"
},
"locationId": "v7cNVAmbTJ7ju6Tfco2n",
"lastActionDate": "2026-05-08T06:03:36.595Z",
"indexVersion": 6,
"customFields": [
{
"id": "juyJof8eaS5pYVigGdit",
"fieldValue": "69ddab4e6224823220635093"
}
],
"followers": [],
"contact": {
"id": "MOsU2dtyy4kersU2CTdV",
"name": "Test GHL 2",
"email": "<my-email>",
"phone": "+15558675309",
"tags": [],
"followers": []
}
},
"traceId": "9f21a0d9-8589-443d-87b9-1dcf0bb0f29c"
}Product Area
opportunities
📋 Use Case
I'm trying to surface some Opportunity information, including Notes, in my application so that users have visibility to the most up-to-date GoHighLevel data and can make better decisions as a result.
🚨 Why Should This Be Prioritized?
Developers are wasting time planning and building API integrations based on incorrect documentation.
🧠 Additional Context
No response
🐛 Describe the Bug
The docs for GET Opportunity say that a
notesarray will be included with the response, but no such array is included in the response.📍 API Endpoint
/opportunities/:id
✅ Expected Behavior
Notes associated with the Opportunity should be included in the response as the documentation specifies; or the documentation should be changed to reflect the actual API response.
💻 Screenshots or Code Samples
{ "opportunity": { "id": "PxSlfYH0jrTWDyPGcSBf", "name": "GHL Test 6", "monetaryValue": 0, "pipelineId": "GbkXdmJw023wjgiPsUNH", "pipelineStageId": "047383b5-4054-4c72-9bd6-bb34d8ba823b", "status": "won", "lastStatusChangeAt": "2026-04-14T16:59:12.771Z", "lastStageChangeAt": "2026-05-08T06:03:36.595Z", "createdAt": "2026-04-14T03:07:53.314Z", "updatedAt": "2026-05-08T06:03:36.608Z", "contactId": "MOsU2dtyy4kersU2CTdV", "isAttribute": false, "internalSource": { "type": "CREATED", "id": "69cdd5cb22015948f12dc8e1-mngvs024", "apiVersion": "2021-07-28", "channel": "OAUTH", "source": "INTEGRATION" }, "locationId": "v7cNVAmbTJ7ju6Tfco2n", "lastActionDate": "2026-05-08T06:03:36.595Z", "indexVersion": 6, "customFields": [ { "id": "juyJof8eaS5pYVigGdit", "fieldValue": "69ddab4e6224823220635093" } ], "followers": [], "contact": { "id": "MOsU2dtyy4kersU2CTdV", "name": "Test GHL 2", "email": "<my-email>", "phone": "+15558675309", "tags": [], "followers": [] } }, "traceId": "9f21a0d9-8589-443d-87b9-1dcf0bb0f29c" }Product Area
opportunities
📋 Use Case
I'm trying to surface some Opportunity information, including Notes, in my application so that users have visibility to the most up-to-date GoHighLevel data and can make better decisions as a result.
🚨 Why Should This Be Prioritized?
Developers are wasting time planning and building API integrations based on incorrect documentation.
🧠 Additional Context
No response