IBL MET-SWIM Demonstration Server

Welcome to the demo server of the IBL SWIM Weather. Our focus for the near term is on:

• compliance with the EU Common Project Regulation (CP1)
• interoperability testing with organisations providing MET-SWIM services
• alignment of the AMQP notification structure between the data providers in the EUR region

Beyond CP1, the IBL SWIM Weather product will closely track developments in the community, building MET-SWIM-compatible interfaces. IBL will collaborate with a range of aviation meteorological services to publish value-added products through EDR.

SWIM Weather implements services in compliance with SWIM service definitions as described on the SWIM Registry: IWXXM METAR-SPECI, TAF, SIGMET Subscription and Request Service 1.0.

Data Type	AMQP	EDR
IWXXM METAR/SPECI
IWXXM TAF
IWXXM SIGMET

	Note
	Since December 17th, 2025, and the upgrade to SWIM Weather 1.2.0, anonymous access to EDR and AMQP endpoints has been discontinued. Please read below how to request login credentials (username and password) for your organisation.

	Warning
	For testing purposes only, the services give access to IWXXM METAR, SPECI, TAF, and SIGMET data from EUROCONTROL member states. The operational use of data downloaded from us is not permitted.

Available interfaces

The table below summarises the available external interfaces.

The port column indicates the default port on which the given SWIM Weather interface is exposed on the host system. The port numbers are configurable.

The authentication scheme specifies the type of credentials required by each interface for access.

Authentication

SWIM Weather only supports TLS connections, and unencrypted communication is not allowed for any of the exposed services.

Client users can connect and authenticate to the services in two ways:

• Using mutual TLS with client certificates issued by a CA compliant with EACP, together with a username and password sent over the TLS connection.
• Using server TLS with a username and password sent securely over the TLS connection.

See Authentication for more details.

Requesting API Credentials

In both the mutual and server TLS cases, an additional username and password must be provided. To request your credentials for access to the AMQPS and OGC EDR services, send an email to swimweather-support@iblsoft.com with:

• Your preferred username
• Your organisation name
• An email contact of a person in your organisation that we can reach out to, for example, when there are any changes to how the authentication is handled.
• International phone number to which we can send your password (to avoid storing plaintext passwords in emails).
  • In this case, you will receive a text message from the IBL SMS gateway (this will be a Slovak phone number starting with +421 and ending in 352).
  • We will not store your phone number; it will only be used once for sending the password.

If you want to test using client certificates, please also read the section below for additional information that needs to be provided.

Optional Client Certificate Verification

Users can be authenticated by providing client certificates issued by HARICA, the Certificate Authority (CA) chosen by EUROCONTROL as its partner for implementing the European Aviation Common Public Key Infrastructure (EACP).

If you wish to use mutual TLS and you have a client certificate issued by the HARICA operational or staging environment, we need to add your client certificate details to a whitelist. In this case, please include in the email also this information from the client certificate:

• Common Name (CN)
• Organization (O)
• Email

Alternatively, you can display the contents of your certificate using the following openssl command and include the output in the email:

openssl x509 -in client.crt --text --noout

See also Working with Certificates for more details.