SDK reference now available for the SailPoint PowerShell and Python SDKs

Reference documentation and examples now available for the SailPoint PowerShell and Python SDKs

We are excited to announce that our PowerShell and Python SDKs now have a complete reference of all methods and models for each version of our public API.

Up until now, our SDK docs did not have a detailed reference of all the available methods and models, making it difficult for implementors to use the SDKs. With this addition, implementors now have a complete reference of the available methods and data models, taking the guesswork out of using the SDKs.

SDK examples in the API specification

Each endpoint in our API specification now provides an example of how to invoke that endpoint from SailPoint’s PowerShell or Python SDK. This makes it quicker and easier to utilize our APIs in your code by providing you a relevant example directly in the API specification.

Seamless navigation between the SDK reference and API specifications

The SDK example in the API specification provides a direct link to the SDK method for quicker navigation to the full reference.

Each SDK method document also provides a link to the corresponding API endpoint.

This cross-linking promotes seamless navigation so you can spend more time coding and less time navigating the documentation.

What’s next?

SailPoint currently offers four SDKs:

We are working on providing SDK references for our remaining SDKs, Go and TypeScript. Stay tuned for an announcement on the next SDK reference we release.

5 Likes

This is such a life saver! Kudos to the team :clap:

3 Likes

Hi @colin_mckibben,

This is a fantastic improvement.

Having full method and model references for the PowerShell and Python SDKs really helps close the documentation gap many of us have been navigating. The inline examples and direct links from the API spec to SDK methods make the integration experience smoother and faster — much appreciated!

Regarding the TypeScript SDK (which I also love):
From what I understand, the SDKs don’t auto-generate methods for every new endpoint as SailPoint exposes them. The SDKs typically wrap a curated subset of API functionality; the most commonly used endpoints and models and then update over time. So while they may cover large portions of the API, not everything is immediately available via a native method unless explicitly added by the SDK maintainers.

If there’s an API I want to call that isn’t covered by the SDK yet, I can still use fetch() or axios with an access token correct? A formal method reference (like now provided for Python and PowerShell) for TypeScript would make a big difference.