Introduction

The public AS2Expert API exposes query and automation operations for stations, partners, certificates, messages, webhooks, and operational metrics.

POST https://free.as2expert.com/api/v1/*

In the current version all documented endpoints are consumed via HTTP POST and require a Bearer token in the Authorization header.

General conventions
TopicDetail
Base URLhttps://free.as2expert.com/api/v1
MethodPOST for both read and write operations in this version
AuthenticationAuthorization: Bearer <token>
Content-Typeapplication/json
Success response{"status":"success","data":...} or {"status":"success","total":n,"data":[...]}
Error response{"status":"error","msg":"..."}
POST Endpoint catalog
RouteScopesDescription
/stationsreadList stations visible in the current domain
/stations/detailreadReturn extended station details
/stations/statsreadOperational totals and success rate for a station or folder context
/stations/createwrite / adminCreate a station using internal KMR logic
/partnersreadList partners, optionally filtered by station
/partners/detailreadReturn extended partner details
/partners/createwrite / adminCreate a trading partner
/certificatesreadList certificates available in the current environment
/certificates/detailreadReturn full certificate metadata
/certificates/createwrite / adminGenerate self-signed certificates
/messagesreadList recent messages
/messages/detailreadReturn basic message details
/messages/downloadreadReturn the binary message content in base64
/messages/sendwrite / adminSend one or more AS2 documents
/webhooks/configurewriteConfigure webhooks per partner
/webhooks/getreadGet a partner webhook configuration
/webhooks/testwriteTrigger a test webhook
/webhooks/logsreadList webhook delivery logs
/dashboard/kpisreadQuick summary of activity and success rate for the last 30 days
POST Working examples

The examples below use the public Free environment that is currently published and validated: https://free.as2expert.com/api/v1.

curl
curl
curl -X POST "https://free.as2expert.com/api/v1/stations"   -H "Authorization: Bearer $API_TOKEN"   -H "Content-Type: application/json"   -d '{}'
Python
Python
import requests

BASE_URL = "https://free.as2expert.com/api/v1"
headers = {
    "Authorization": "Bearer TU_TOKEN",
    "Content-Type": "application/json",
}

response = requests.post(
    f"{BASE_URL}/dashboard/kpis",
    headers=headers,
    json={}
)
print(response.json())
JavaScript
JavaScript
const response = await fetch("https://free.as2expert.com/api/v1/messages", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_TOKEN",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({ limit: 10 })
});

const data = await response.json();
console.log(data);
POST Legacy compatibility

The main documentation uses canonical English routes and payload keys. Legacy Spanish aliases remain accepted for compatibility, but they are intentionally kept secondary to avoid polluting the primary reading flow.

CanonicalLegacy aliasNotes
/stations/estacionesBoth published in Free
/messages/detail/mensajes/detalleBoth require numeric id
/webhooks/get/webhooks/obtenerBoth published in Free
POST Scopes
ScopeUsage
readQueries, lists, detail views, metrics, and log reading
writeEntity creation, message sending, and webhook configuration
adminAllows write operations on endpoints that accept write/admin
POST Trust and release evidence

The public API focuses on business integrations. Trust lifecycle, TSA verification, and compliance gates are governed by the product UI plus internal backend objects.

SurfacePurpose
Socios / Trust LifecyclePrepare next certificates, schedule rollover, activate it, retire it, and read the event timeline.
Certificados / Usage / LifecycleSee where a certificate is current, where it is next, and which partners are affected.
TsaProfilesConfigure TSA endpoints, trust material, and run real RFC3161 validation.
ComplianceRunStartExecute release canaries and persist pass/warn/fail evidence for the chosen release tag.
ComplianceReleaseExportAggregate a release tag into a single gate verdict and export a readable markdown summary.

This layer is intentionally kept outside the public Free API because it is an operator governance surface, not a generic third-party integration contract.