Skip to main content
POST

Description

The credentials object structure depends on the deliveryMethod:
  • SFTP: Use SFTPCredentials schema (host, port, username, password, remotePath)
  • FTP: Use SFTPCredentials schema with port 21
  • HTTP/HTTPS: Use HTTPCredentials schema (apiUrl, authType, bearerToken/apiKey)
  • AS2: Use AS2Credentials schema (endpoint, as2From, as2To)
  • WebDAV: Use WebDAVCredentials schema (url, username, password)
Credentials are encrypted at rest using PostgreSQL pgcrypto. Authorization:
  • Required role: owner only

Code Examples

Authorizations

Authorization
string
header
required

JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"

Body

application/json
providerId
string<uuid>
required

ID of the DDEX provider from the provider catalog

deliveryMethod
enum<string>
required

Delivery protocol to use

Available options:
SFTP,
FTP,
HTTP,
HTTPS,
AS2,
WebDAV
credentials
object
required

Credentials for SFTP/FTP delivery method

labelId
string<uuid> | null

Optional label ID for label-specific configuration

customSettings
object

Provider-specific custom settings

priority
integer
default:50

Priority for this provider (higher = preferred)

rateLimits
object

Rate limiting configuration

acknowledgementSettings
object

MDN/acknowledgement settings

Response

Created

status
string
data
object