SDKs
Quick answer
SailPoint provides SDKs (e.g. Python, TypeScript) that wrap authentication and endpoints so you call the APIs with typed methods instead of raw HTTP.
Key takeaways
- Official SDKs wrap auth and endpoints
- Available for languages like Python and TypeScript
- Handle tokens, retries and pagination
- Faster than hand-rolling HTTP
SailPoint publishes official SDKs (for languages such as Python and TypeScript) that wrap the REST API in typed methods. They remove the boilerplate of authentication, pagination and retries, so you write intent (“list these identities”) rather than plumbing (“get a token, loop offsets, handle 429”).
What the SDKs give you
- Authentication handled, the SDK obtains and refreshes OAuth tokens.
- Typed endpoints, methods and models for each resource, with editor autocomplete.
- Pagination helpers, iterate whole collections without managing offsets by hand.
- Retry/backoff for transient errors in many cases.
Why prefer an SDK
Hand-rolled HTTP works, but you end up re-implementing token management, pagination and error handling, and maintaining it as the API evolves. The SDK centralises all of that, so your integration is shorter, less error-prone and easier to keep current. For anything beyond a one-off script, reach for the SDK first.
Practical guidance
- Pin the SDK version and upgrade deliberately.
- Keep credentials in a secret store, pass them to the SDK at runtime.
- Use the built-in pagination rather than manual loops.
Common pitfalls
- Reinventing auth/pagination with raw HTTP when the SDK does it.
- Floating (unpinned) SDK versions causing surprise breakage.
- Embedding secrets rather than injecting them.
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 do SDKs provide?
- A. Typed wrappers around authentication and API endpoints.
- B. Token management, retries and often pagination.
- C. Less boilerplate and fewer errors than raw HTTP.
Show answer
A. Typed wrappers around authentication and API endpoints.
Typed wrappers around authentication and API endpoints.
What do SDKs handle for you?
- A. Typed wrappers around authentication and API endpoints.
- B. Less boilerplate and fewer errors than raw HTTP.
- C. Token management, retries and often pagination.
Show answer
C. Token management, retries and often pagination.
Token management, retries and often pagination.
Why prefer an SDK?
- A. Token management, retries and often pagination.
- B. Less boilerplate and fewer errors than raw HTTP.
- C. Typed wrappers around authentication and API endpoints.
Show answer
B. Less boilerplate and fewer errors than raw HTTP.
Less boilerplate and fewer errors than raw HTTP.