DOC-827 | Graph Analytics: Clarify descriptions and endpoint URL paths #841
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Upstream PRs
Note
Clarifies Graph Analytics docs with explicit AI Data Platform vs AMP URL structures, authentication guidance, and standardized cURL examples across Management and Engine APIs.
AI service,Management API, andEngine APIwith explicit paths (e.g.,https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/…,https://<APPLICATION_ENDPOINT>:8829/graph-analytics/api/graphanalytics/v1/…).oasisctl login, JWT session tokens), with bearer header examples and verification calls.graphanalyticsservices and list/deploy/get/delete engines; include placeholder values and info callouts.loaddata, algorithms (pagerank,wcc,scc,betweennesscentrality,linerank), and results management.storeresults, job lifecycle (/v1/jobslist/get/delete), and graph lifecycle (/v1/graphslist/get/delete).EXTERNAL_ENDPOINT,SERVICE_ID,APPLICATION_ENDPOINT,ENGINE_ID) and tips to simplify requests; add info/tip blocks and sample responses.Written by Cursor Bugbot for commit 445eea5. This will update automatically on new commits. Configure here.