Frequently Asked Questions

What do I need to use the Beopen API?

First of all you need to register on the Developer Portal with a valid e-mail address.  Once done, you can immediately test the SMS API in Sandbox mode. This allows you to start developing and testing the API. Once you finished your development, you need to request a promotion to Production. If promoted and approved (only the first promotion needs to be approved by Belgacom) your application can start sending SMS.

A detailed overview can be found in the Developer Quick Start Guide in the Resource section.

What does it cost?

Registering on the Developer Portal and testing in Sandbox mode is free of charge.  In production mode you will be charged only for the SMS sent and received (Pay as you use). The price per message is volume based. Registering keywords (for receiving SMS MO) will be invoiced. A detailed overview on pricing can be found in the Tariffs section.

I want to send SMS to international destinations.

By default SMS to international destinations is blocked. Contact us if you want to be able to send SMS to international destinations.

I want to use my own MSISDN as sender address

Besides using the shared shortcode 8937 as sender address, you can also request your own MSISDN as sender address. Since we need to check the number is owned by the requestor, we can only accept an active billable Proximus/Belgacom postpaid number.

When I try to use the API, a policy error is generated.

Please find below the possible errorcodes:

Error Explanation
POL-006 TPA exceeded its maximum allowed rate of transactions The maximum rate of transactions is exceeded. Ensure that the rate of your requests is within the limits set up in your SLA, e.g. 10 TPS (Transactions Per Second).
POL-008: TPA is invalid The Third Party Application authentication details are incorrect. Check your basic authentication username and password are correct and re-submit your request.
POL-010 Subscriber target not authorized Authorisation from the subscriber has not been obtained through the Consent service. Please request authorisation for this subscriber through the Consent Service.
POL-014 White List is enforced, and address is not in White List A white list is enforced and the number is not in the white list. Check your SLA details.
POL-015 Black List is enforced, and address is in Black List A black list is enforced and the number is in the black list. Check you SLA details.
POL-016 Max Requests is enforced, and max requests has been exceeded The maximum number of requests for this service is exceeded. Contact the support team.
POL-017 Operation is not allowed The method/operation is not supported in your current SLA. Check your SLA and use a method that is supported.
POL-020 Max Message Length is enforced, and max message length has been exceeded A maximum message length policy is in place and you have exceeded this. Check you SLA for the maximum message length, update your message and re-submit your request.
POL-021 Min Message Length is enforced, and message length is less than min allowed A minimum message length policy is in place and you have a message length that is less than this minimum. Check your SLA for the maximum message length, update your message and re-submit your request.
POL-022 Receipting is enforced, and receipting has not been enabled A receipt has been requested but it is not enabled for this service. Remove the receipt request and re-submit your request.
POL-040 Max Destination Addresses is enforced and maximum destination addresses has been exceeded A maximum destination address limit is enforced and it has been exceeded. Check your SLA for the limit and re-submit your request.