Authentication

Authentication data must be provided for every call. It is expected as an HTTP authentication (HTTP basic protocol). The user and client login data is transmitted in the format:

USER@CLIENT:PASSWORT

The login data must be base 64–encoded. The password is written out, so this is why we require using HTTPS encryption and the data cannot be intercepted by unauthorized parties.

Example:

The string "API_TEST@APITEST:API_TEST2024", when encoded in base 64, yields “QVBJX1RFU1RAQVBJVEVTVDpBUElfVEVTVDIwMjQ=".

The following line would therefore be added to the HTTP header:
Authorization: Basic QVBJX1RFU1RAQVBJVEVTVDpBUElfVEVTVDIwMjQ

Endpoints

REST (OpenApi)

You have to replace <carrier_connect_system> with the system you want to connect (e.g. demo1cai, test2cai, prod1cai).

https://rz3.aeb.de/<carrier_connect_system>/rest/openapi.json

SOAP

https://rz3.aeb.de/<carrier_connect_system>/servlet/bf/DLCarrierBF?WSDL
https://rz3.aeb.de/<carrier_connect_system>/servlet/bf/doc/DLCarrierBF/de/aeb/xnsg/dl/bf/IDLCarrierBF.html

💡

The API is only available via Secure Socket Layer (SSL).

Test Credentials

Before you can start using the Carrier Connect API, you need a user and a password. AEB will provide them to you.

If you do not have your own client yet, you can use the following credentials to test the API:

❗️

The client "APITEST" is intended for basic connectivity testing and is used by different users. Don't use it with sensitive data.