DevPortalPagoPA




Table of contents

E-service templates

What they are and how they work

E-service templates standardize the creation of e-services for recurring use cases.
When multiple parties need to produce the same e-service, templates ensure the use of the same API and homogeneous features (e.g., name and description).

Template catalog

Templates prepared by creator parties (referred to in the AgID Guidelines as API co-design managers) are published in a dedicated catalog, separate from the e-service catalog.

Use by producing parties

Each authorized producer can:
  1. Browse the template catalog;
  2. Create its own instance of an e-service starting from the selected template.
The instance inherits features identical to those defined in the template, ensuring consistency across multiple producing parties.
An introduction and demo of this feature are available in the dedicated webinar.

Need help?

Open a ticket using the dedicated feature inside your Reserved Area

Tell us what you think

To report problems or give feedback, you can open a report on GitHub