Start here for the Namirial Notify API references.
Use these APIs to submit certified communications, query their status, and retrieve related evidence according to the service you are integrating with.
The following API references are available:
- EviNotice API — submit, query, and retrieve certified hosted notices
- EviMail API — submit and query certified emails
- EviSMS API — submit and query certified SMS messages
- EviPost API — submit and query certified physical postal communications
- Shared download APIs — download attachments by ID
- Namirial Notify OpenAPI — unified OpenAPI reference for the documented Notify APIs
Each reference page includes an overview of the service, authentication details, base URLs, and a link to the OpenAPI specification.
These APIs use HTTP Basic authentication.
Use the credentials provided for your Namirial Notify environment and organisation. Authentication requirements can vary depending on the environment and the services enabled for your account.
Always confirm the credentials, enabled services, and environment details with your Namirial Notify technical contact before starting an integration.
The OpenAPI specifications currently reference these environments:
- Production —
https://api.evicertia.com - Pre-production / QA —
https://api.ecertia.com
Environment availability can depend on your organisation setup and service activation.
- Open the API reference for the service you want to integrate with.
- Review the authentication method and available environments.
- Check the request and response models for the operations you need.
- Read the shared guides for error handling, integration workflows, security and authentication, and performance and scaling.
- Validate field values, enum values, and workflow assumptions with your Namirial Notify SME before going live.
These API references document service-specific REST operations for:
- submitting certified communications
- querying transactions
- retrieving transaction-related data, where supported
Callbacks, webhooks, API collections, and no-code options are documented in their dedicated guides.
Use these shared guides alongside the service reference pages: