X.509 Certificates

Manage digital certificates for signing and encrypting AS2 messages.

POST /api/v1/certificates

List certificates accessible inside the current site.

{
  "status": "success",
  "total": 1,
  "data": [
    {
      "id": 105,
      "email": "as2@example.com",
      "commonname": "free.as2expert.com",
      "commonName": "free.as2expert.com",
      "validitystart": "2026-04-26 12:00:00",
      "validityend": "2027-04-26 12:00:00",
      "station": "My station",
      "station_name": "My station"
    }
  ]
}

POST /api/v1/certificates/detail

Return extended metadata for a specific certificate.

Field	Type	Required
id	integer	Yes

POST /api/v1/certificates/create

Create a self-signed X.509 certificate for your station. In the current version only self_signed mode is supported.

Request body

Field	Type	Required	Description
station	integer	Yes	Station ID
selfSigned	boolean	Yes	Must be true in the current implementation
email	string		Subject email
commonName	string		Certificate common name
countryName	string		ISO country code, for example ES
localityName	string		Locality
provinceName	string		Province or state
organization	string		Organization
organizationUnitName	string		Organizational unit
dias	integer		Validity in days, default 365
keybits	integer		Key size, default 2048
hash	string		Hash algorithm, for example sha256

Ejemplo Python

response = requests.post(
    f"{BASE_URL}/certificates/create",
    headers=headers,
    json={
        "station": 62,
        "selfSigned": True,
        "email": "as2@example.com",
        "commonName": "free.as2expert.com",
        "dias": 730
    }
)

Response

{
  "status": "success",
  "msg": "Certificate created",
  "data": {
    "id": 129,
    "certificate_id": 129,
    "station_id": 62,
    "commonName": "free.as2expert.com",
    "countryName": "ES",
    "localityName": "Madrid"
  }
}

Certificate usage

Certificates are used automatically when you send messages with encrypt: true or sign: true.

The canonical response focuses on metadata. The raw backend payload may still include extended fields such as cert_pem, but integrations should rely on certificate_id and the normalized metadata first.

POST Certificate lifecycle visibility

The product complements certificate metadata with a lifecycle view that shows where a certificate is active now, where it is scheduled as next, and which partners would be affected by a rollover.

Surface	Reading
`Certificados / Usage / Lifecycle`	Current count, next count, and partner-level impact.
`CertificadoLifecycleInfo`	Backend object that resolves current and next partner usage for one certificate.