# Development and integration guides

Resources for integrating with Namirial Notify programmatically or through a supported no-code integration path.

## REST APIs

Namirial Notify exposes REST APIs for certified communication services. You can
use these APIs to submit communications, query their status, and retrieve
related evidence from your own systems.

See the [API reference overview](/it/products/namirialnotify/apis/overview) for authentication,
environments, service guides, and the unified OpenAPI reference.

## Error handling

Use the shared [Error handling](/it/products/namirialnotify/dev/error-handling) guide for HTTP status codes,
service-specific error payload formats, and production recommendations for
client-side error processing.

## Callbacks and webhooks

Namirial Notify can send push notifications to your system when a transaction changes state. See [Callbacks and webhooks](/it/products/namirialnotify/dev/callbacks) for configuration details.

## Integration workflows

See [Integration workflows](/it/products/namirialnotify/dev/integration-patterns) for end-to-end patterns
that combine Submit, callback handling, Query or Get reconciliation, and
affidavit retrieval.

## Security and authentication

See [Security and authentication](/it/products/namirialnotify/dev/security-best-practices) for production
guidance on credential handling, callback hardening, and data-minimization
practices.

## Performance and scaling

See [Performance and scaling](/it/products/namirialnotify/dev/performance-guidelines) for guidance on
callbacks versus polling, pagination, evidence retrieval, and high-volume usage
planning.

## API collections

Ready-to-use API client collections are available for testing and exploring the APIs. See [API collections](/it/products/namirialnotify/dev/postman-collections) for download links and setup instructions.

## QeRDS integration

For qualified EviNotice submission, start with [Integrate QeRDS notices](/it/products/namirialnotify/dev/qerds-integration). It covers issuer credentials and certificate prerequisites, recipient identity, ES/IT request differences and result tracking. See [QeRDS with EviNotice](/it/products/namirialnotify/services/qerds) for the functional explanation.

## QeRDS user registration

A separately enabled registration workflow can start recipient enrollment before a QeRDS EviNotice is sent. It is not required for every QeRDS integration. Confirm [availability and prerequisites](/it/products/namirialnotify/dev/qerds-registration#availability-and-prerequisites) with Namirial, then see the [QeRDS user registration API](/it/products/namirialnotify/dev/qerds-registration) for its endpoint, request fields, response and return URL guidance. AML ID registration and identity reuse are limited to the Italian qualified variant (`QERDS_IT`) and to financial institutions with a specific agreement with Namirial; see [AML ID eligibility](/it/products/namirialnotify/dev/qerds-registration#aml-id-eligibility).

## Communication templates

Custom email templates created in the admin UI can be referenced in API submissions to replace the default system emails. See [Using communication templates from the API](/it/products/namirialnotify/dev/templates) for the EviNotice template parameters and examples.

## No-code integration

If you prefer to integrate without writing code, Namirial Notify supports integration through certifica.me. See [No-code integration](/it/products/namirialnotify/dev/no-code-certificame) for details.