Storage Configuration

The storage configuration controls where TaprNext stores PEPPOL message files, including inbound XML, outbound XML, and attachments.

Storage Options

Three backend choices are available:

Default — Platform-managed storage with zero configuration required. Files remain on TaprNext servers and are accessible via Invoice Manager and the API. Ideal for most users getting started.

S3 — Store files in your own AWS S3 bucket or S3-compatible service for complete control over file storage and access.

API — No file storage on the platform. Each PEPPOL message forwards via HTTP POST to your specified callback URL instead.

S3 Configuration

To use S3 storage, provide these credentials:

Field	Description
AWS Access Key	Your IAM user’s access key
AWS Secret Key	Your IAM user’s secret key
AWS Region	e.g., eu-central-1
S3 Bucket Name	Your bucket name
Endpoint URL	Leave blank for AWS; set for S3-compatible services
Presign Expiry	Download link expiration in seconds (default: 3600)
Max File Size	Maximum file size in MB (default: 10)

Your IAM user requires these permissions: s3:GetObject, s3:PutObject, and s3:ListBucket.

TaprNext validates connectivity, bucket accessibility, and permissions when you save the configuration.

API Callback Configuration

When using API mode, configure your callback endpoint:

Field	Description
API Callback URL	HTTPS endpoint to receive messages (required)
API Timeout	Request timeout in seconds (default: 30)

The URL must use HTTPS. Private IP ranges, loopback addresses, and link-local addresses are blocked for security.

Authentication options include Bearer Token, API Key Header, or Basic Auth. You may add custom headers as JSON and optionally log a specific response field.

Plan Requirements

Plan	Available Options
Free & Starter	Default only
Growth & Enterprise	Default, S3, and API