Examples
Quick answer
Practical examples: fetch an identity, submit an access request, list a certification, and search entitlements, the calls you will make most.
Key takeaways
- Fetch and search identities
- Submit access requests
- Read certifications and campaigns
- Search entitlements and roles
The fastest way to learn the SailPoint API is by working through the calls you will actually make most: fetching and searching identities, submitting access requests, and reading certification and audit data. Each is a straightforward authenticated REST call, usually with a filter.
Search for an identity
GET /v3/public-identities?filters=alias eq "jdoe"
Authorization: Bearer <token>Submit an access request
POST /v3/access-requests
Authorization: Bearer <token>
Content-Type: application/json
{
"requestedFor": ["<identityId>"],
"requestType": "GRANT_ACCESS",
"requestedItems": [{ "type": "ACCESS_PROFILE", "id": "<id>" }]
}Read certification data
Pull campaign and certification detail to build reporting or feed downstream systems, combining filtering to scope the data and pagination to retrieve it in full.
Turn these into robust code
Start from these patterns and add the production essentials: obtain and refresh an OAuth token, filter server-side, paginate large results, and back off on 429/5xx. The official SDKs bundle most of this for you.
Common pitfalls
- Copying examples without adding pagination for bulk reads.
- Hard-coding IDs instead of looking them up.
- Skipping error handling that production needs.
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
What are the most common API calls?
- A. Combine calls with pagination and backoff.
- B. A bearer token and often a filter expression.
- C. Fetching/searching identities, submitting access requests, and reading certifications.
Show answer
C. Fetching/searching identities, submitting access requests, and reading certifications.
Fetching/searching identities, submitting access requests, and reading certifications.
What do most calls need?
- A. Fetching/searching identities, submitting access requests, and reading certifications.
- B. A bearer token and often a filter expression.
- C. Combine calls with pagination and backoff.
Show answer
B. A bearer token and often a filter expression.
A bearer token and often a filter expression.
How do you read in bulk?
- A. A bearer token and often a filter expression.
- B. Fetching/searching identities, submitting access requests, and reading certifications.
- C. Combine calls with pagination and backoff.
Show answer
C. Combine calls with pagination and backoff.
Combine calls with pagination and backoff.