Skip to content
IT Canvass
Reference · Lesson

Java API reference

Quick answer

Orientation to the SailPoint IdentityIQ Java API: SailPointContext, key classes and common calls used in rules and tasks.

Key takeaways

  • context is the API entry point
  • Core classes: Identity, Link, Bundle, ProvisioningPlan, Filter
  • Use QueryOptions + projection for efficient reads
  • Commit only when needed; decache in long loops

SailPointContext

The SailPointContext (context) is the entry point: getObject, getObjectByName, search, saveObject, commitTransaction and decache are the calls you use most.

Key classes

Identity, Link, Application, Bundle, ManagedAttribute, ProvisioningPlan and Filter are the classes you manipulate in rules and tasks.

Querying efficiently

Use QueryOptions with filters and projection columns via context.search to avoid loading full objects when you only need a few fields.

Saving safely

Save and commit only when needed, and decache long-running loops to keep memory under control.

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

  1. What is the entry point to the IdentityIQ Java API?

    • A. Filter
    • B. SailPointContext
    • C. Bundle
    • D. WorkItem
    Show answer

    B. SailPointContext

    SailPointContext (context) is the gateway for all object operations.

Frequently asked questions

What does the term Java API Reference refer to in SailPoint?

The SailPointContext (context) is the entry point: getObject, getObjectByName, search, saveObject, commitTransaction and decache are the calls you use most.

What is worth remembering about Java API Reference in practice?

Identity, Link, Application, Bundle, ManagedAttribute, ProvisioningPlan and Filter are the classes you manipulate in rules and tasks.

What is another point to note about Java API Reference?

Use QueryOptions with filters and projection columns via context.
CallWhatsAppEnquire