ScriptRunner HAPI API Skill

Use the bundled HAPI JAR as the authority for available Cloud HAPI bytecode signatures. The normal lookup command reads class files with javap; it does not load or execute HAPI classes.

Required workflow

1. Read the target product guidance from scriptrunner-platform-guidance first.
2. Find a class when necessary:
   • sms-hapi-lookup --product jira --search Issues
   • sms-hapi-lookup --product confluence --search Pages
3. Inspect every class used by generated HAPI code:
   • sms-hapi-lookup --product jira com.adaptavist.hapi.cloud.jira.issues.Issues
   • sms-hapi-lookup --product confluence com.adaptavist.hapi.cloud.confluence.pages.Pages
4. Use --member <name> to narrow large classes. The command follows HAPI superclasses and @DelegatesTo targets by default; with --depth 0 it still names them under "Related but not expanded" so nothing is hidden.
5. Inspect return types before chaining. Run a separate lookup for a returned HAPI class when its members are not already shown.
6. Pair signature evidence with the bundled ScriptRunner documentation for behaviour, examples, permissions, and platform constraints. A method's presence does not prove it is appropriate in every script context.
7. Validate the final Groovy with sms-groovy-check --platform cloud --product jira|confluence --context <context>.

Commands