REST API FOR YOUR OWN SYSTEMS

Connect your applications to mailfino

Use the REST API to connect contacts, audiences and newsletter tasks to your own applications — in the cloud, self-hosted or with Enterprise.

Illustration of a REST API connection between a code editor and mailfino.

A clear data flow

Bring your application data into email marketing

Connect the tasks your application needs, from contact updates to newsletter preparation and reporting.

01 · Source

Your own system

Start with data from your CRM, business application, customer portal or custom service.

→

02 · Connection

REST API

Connect through the REST API using Bearer token authentication.

→

03 · Processing

mailfino

Contacts, lists, forms or prepared content are processed in the intended account.

→

04 · Result

Sending and reporting

Newsletters are sent and the results are analyzed in the mailfino report.

Typical use cases

Automate the handovers that take up your time today

The REST API is particularly useful when structured data is already available or newsletter workflows need to become part of your own application.

Synchronize contacts

Map recipients, lists, fields and tags from a CRM, portal or specialist application to mailfino.

Prepare newsletter workflows

Integrate drafts, templates and sending jobs into your own workflows using the resources documented for these purposes.

Process feedback

Incorporate form submissions, unsubscribes and complaints into connected processes.

Cloud, Selfhosting and Enterprise

Use the API with the right deployment model

The available resources depend on the account and product variant. Choose deployment in the mailfino Cloud, on your own infrastructure or as a tailored Enterprise solution.

Cloud

Get started directly in the Cloud

mailfino operates the platform. Your application uses the API access provided for the account, without you having to operate mailfino yourself.

Self-hosting

Run it in your own environment

The base URL, connectivity and operation are part of your infrastructure. The documented interface is available there for your integration.

Enterprise

Meet individual requirements

For more complex integration, operational and security requirements, the API is included in a tailored Enterprise offering.

A documented foundation

Build with Swagger and OpenAPI

REST API v6 is documented through Swagger UI and OpenAPI. It uses JSON and Bearer token authentication and can be used in Cloud, Selfhosting and tailored Enterprise projects.

  • Documented endpoints at /api/v6/
  • Swagger UI and OpenAPI specification as the technical reference
  • Available resources depend on the account and product variant

# Read data through the API
GET /api/v6/Category
Authorization: Bearer BEARER_TOKEN
Accept: application/json

Ready to build your own integration?

FAQ

Frequently asked questions about the mailfino REST API

How is the REST API authenticated?

The integration uses Bearer token authentication. The specific access belongs to the respective account and deployment model.

Which areas does the API cover?

Documented resources include recipients, list structures, fields, tags, forms, drafts, templates, sending jobs, unsubscribes and complaints. The current Swagger documentation remains authoritative.

Can mailfino be connected to a custom application?

Yes. The REST API provides the technical foundation for custom applications, portals and individual workflows. The specific data flow depends on the required resources and permissions.

Does the API work with Cloud, Selfhosting and Enterprise?

The API can be used with the respective mailfino deployment model. The base URL, access, operational responsibilities and individual project scope differ depending on the variant.

Where can I find the technical documentation?

See the Swagger documentation for the current endpoints and data models.