enonic-api-reference

To find the Enonic XP lib-portal function signature and parameters, query the API reference to extract exact import blocks, parameter tables, return types, and minimal working examples directly from official reference files.

The correct import block and return type for lib-content functions in Enonic XP are documented in the API reference, which provides structured details including function signatures, parameter types, and usage examples for content operations.

Yes, the Enonic XP API reference covers lib-auth, lib-node, lib-task, lib-content, lib-portal, lib-context, lib-event, lib-io, lib-mail, lib-repo, and lib-schema, providing accurate function signatures and usage examples across all these server-side libraries.

To get usage examples for lib-context in Enonic XP server-side development, request the API reference details to receive a minimal working example alongside the function signature, parameter table, and return type extracted from the official documentation.

Yes, you can use the Enonic XP API reference to check version compatibility for lib-io functions, as it notes specific XP version requirements from the official docs when extracting function signatures, parameters, and return types.

Cross-library tasks like content creation and authentication in Enonic XP have no documented limitations in the reference; it provides end-to-end guidance across libraries with accurate function signatures, import blocks, and version compatibility notes.