# 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 [API documentation](/products/namirialnotify/dev/api-documentation) for authentication,
environments, service guides, and the unified OpenAPI reference.

## Error handling

Use the shared [Error handling](/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](/products/namirialnotify/dev/callbacks) for configuration details.

## Integration workflows

See [Integration workflows](/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](/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](/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](/products/namirialnotify/dev/postman-collections) for download links and setup instructions.

## QERDS user registration

The QERDS identity verification service exposes a separate API for pre-registering recipients before sending a QERDS EviNotice. See [QERDS user registration API](/products/namirialnotify/dev/qerds-registration) for the endpoint, request fields, response schema, and return URL error codes.

## 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](/products/namirialnotify/dev/templates) for the EviSign and 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](/products/namirialnotify/dev/no-code-certificame) for details.