Switch to Dutch
  Need help?

Introduction Last update: February 2023

Before you can use our API you need a Billink username and an uid. If you have not yet received it, we advise you to contact our customer service. Our customer service is open from Monday to Thursday from 9:00 AM to 8:00 PM, on fridays from 9:00 AM till 5:00 PM and can be reached on [email protected] or 010 - 414 14 73.

To make the process clearer, we like to explain how our system works. A Check API must be carried out for each order to check the creditworthiness of a consumer. When a consumer is carried out creditworthy you will receive a CHECK-UIDD from us. This CHECK-UIDD is required to add the order via the order API.

API's

Check API

On our check we check the creditworthiness of the consumer. This API Call is obliged when placing an order. When the consumer is creditworthy, we respond with code 500 and the CHECK-UUID. With this CHECK-UUID you can send a request with the orderdetails to the Order API. When the consumer is rejected, we return code 501.

For the check API we need the following values:
VERSION In all cases this is "Billink2.0".
CLIENTUSERNAME Your Billink Username.
CLIENTID Your unique API key.
ACTION In all cases this is "check".
TYPE "P" for individuals, "B" for business orders.
WORKFLOWNUMBER "1" for the standard workflow.
FIRSTNAME Consumer's first name.
LASTNAME The surname of the consumer including insert.
INITIALS Initials (this field is not required).
STREET Street name of the billing address.
HOUSENUMBER House number of the billing address.
HOUSEEXTENSION Extension of the billing address.
POSTALCODE Postal code of the billing address.
CITY City of the billing address.
COUNTRYCODE Country code of the billing address (ISO3166-1 ALPHA-2).
PHONENUMBER Consumer telephone number.
BIRTHDATE Date of birth (only with type P orders).
COMPANYNAME Company name (only at type B orders).
CHAMBEROFCOMMERCE Chamber of Commerce number (only at type B orders).
EMAIL E-mail address
ORDERAMOUNT Total order amount including VAT.
IP IP address of the consumer.
DELIVERYSTEET Street of the delivery address.
DELIVERYHOUSENUMBER House number of the delivery address.
DELIVERYHOUSEEXTENSION Extension of the delivery address.
DELIVERYPOSTALCODE Postal code of the delivery address.
DELIVERYCITY City of the delivery address.
DELIVERYCOUNTRYCODE Country code of the delivery address (ISO3166-1 ALPHA-2).
Example Check API Private Order:
POST: https://test.billink.nl/api/check or https://client.billink.nl/api/check 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>check</ACTION>
		<TYPE>p</TYPE>
		<WORKFLOWNUMBER>1</WORKFLOWNUMBER>
		<FIRSTNAME>Test</FIRSTNAME>
		<LASTNAME>Test</LASTNAME>
		<INITIALS>T</INITIALS>
		<STREET>Wilhelminakade</STREET>
		<HOUSENUMBER>159</HOUSENUMBER>
		<HOUSEEXTENSION>A</HOUSEEXTENSION>
		<POSTALCODE>3072AP</POSTALCODE>
		<CITY>Rotterdam</CITY>
		<COUNTRYCODE>NL</COUNTRYCODE>
		<PHONENUMBER>0104141473</PHONENUMBER>
		<BIRTHDATE>01-01-1985</BIRTHDATE>
		<EMAIL>[email protected]</EMAIL>
		<ORDERAMOUNT>100</ORDERAMOUNT>
		<IP>172.2.168.1</IP>
		<DELIVERYSTEET>Wilhelminakade</DELIVERYSTEET>
		<DELIVERYHOUSENUMBER>159</DELIVERYHOUSENUMBER>
		<DELIVERYHOUSEEXTENSION>B</DELIVERYHOUSEEXTENSION>
		<DELIVERYPOSTALCODE>3072AP</DELIVERYPOSTALCODE>
		<DELIVERYCITY>Rotterdam</DELIVERYCITY>
		<DELIVERYCOUNTRYCODE>NL</DELIVERYCOUNTRYCODE>
	</API>
Example CHECK API Business Order:
POST: https://test.billink.nl/api/check or https://client.billink.nl/api/check 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>check</ACTION>
		<TYPE>b</TYPE>
		<WORKFLOWNUMBER>1</WORKFLOWNUMBER>
		<FIRSTNAME>Test</FIRSTNAME>
		<LASTNAME>Test</LASTNAME>
		<INITIALS>T</INITIALS>
		<STREET>Wilhelminakade</STREET>
		<HOUSENUMBER>159</HOUSENUMBER>
		<HOUSEEXTENSION>A</HOUSEEXTENSION>
		<POSTALCODE>3072AP</POSTALCODE>
		<CITY>Rotterdam</CITY>
		<COUNTRYCODE>NL</COUNTRYCODE>
		<PHONENUMBER>0104141473</PHONENUMBER>
		<COMPANYNAME>Billink B.V.</COMPANYNAME>
		<CHAMBEROFCOMMERCE>12345678</CHAMBEROFCOMMERCE>
		<EMAIL>[email protected]</EMAIL>
		<ORDERAMOUNT>100</ORDERAMOUNT>
		<IP>172.2.168.1</IP>
		<DELIVERYSTEET>Wilhelminakade</DELIVERYSTEET>
		<DELIVERYHOUSENUMBER>159</DELIVERYHOUSENUMBER>
		<DELIVERYHOUSEEXTENSION>B</DELIVERYHOUSEEXTENSION>
		<DELIVERYPOSTALCODE>3072AP</DELIVERYPOSTALCODE>
		<DELIVERYCITY>Rotterdam</DELIVERYCITY>
		<DELIVERYCOUNTRYCODE>NL</DELIVERYCOUNTRYCODE>
	</API>
Example Response approval:

	<API>
		<RESULT>MSG</RESULT>
		<MSG>
			<CODE>500</CODE>
			<DESCRIPTION>Advies=1</DESCRIPTION>
		</MSG>
		<UUID>XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</UUID>
	</API>
Example Response Rejection:

	<API>
		<RESULT>MSG</RESULT>
		<MSG>
			<CODE>501</CODE>
			<DESCRIPTION>Advies=0</DESCRIPTION>
		</MSG>
	</API>

In addition to rejections, it is also prevents data that is incomplete. There are separate error codes for this.
These can be found here.

Order API

You can use the Order API to add orders. To add an order, we need a CHECK-UUID.

We need the following values for the order API. Fields marked with a "*" are optional.
VERSION In all cases this is "Billink2.0"
CLIENTUSERNAME Your Billink Username
CLIENTID Your unique API key
ACTION In all cases this is "order"
TYPE "P" for individuals, "B" for business orders
WORKFLOWNUMBER "1" for the standard workflow
ORDERNUMBER The invoice number that the order must receive
DATE The order date to be shown on the invoice
FIRSTNAME The first name of the consumer
LASTNAME The surname of the consumer including insert
SEX The gender of the consumer (only at type P orders (M, V or O)
INITIALS* initials
STREET Street name of the billing address
HOUSENUMBER House number of the billing address
HOUSEEXTENSION* Extension of the invoice address
POSTALCODE Postal code of the Invoice Address
CITY City of the billing address
COUNTRYCODE Country code of the Invoice Address (ISO3166-1 ALPHA-2)
PHONENUMBER Consumer telephone number
BIRTHDATE Date of birth (only at type P orders)
COMPANYNAME Company name (only at type B orders)
CHAMBEROFCOMMERCE Chamber of Commerce number (only at type B orders)
EMAIL E-mail address
EMAIL2* Second recipient email address
IP Consumer IP address
DELIVERYSTEET* Street of the delivery address
DELIVERYHOUSENUMBER* House number of the delivery address
DELIVERYHOUSEEXTENSION* Extension of the delivery address
DELIVERYPOSTALCODE* Postal code of the delivery address
DELIVERYCITY* City of the delivery address
DELIVERYCOUNTRYCODE* Country code of the delivery address (ISO3166-1 ALPHA-2)
ADITIONALTEXT* Added text for the invoice
TRACKANDTRACE* trackAndTraceCode
VATNUMBER* Consumer VAT number
CHECKUUID Use the value from the CHECK API
CURRENCY* Only applicable to orders outside of Europe (EUR, USD or GBP)
STATE* Only applicable to orders outside of Europe
LOCALITY* Only applicable to orders outside of Europe
CODE Article number of the product
DESCRIPTION Description of the product
ORDERQUANTITY The amount of products
PRICEINCL Use at Type P orders
PRICEEXCL Use at Type B Orders
BTW "0", "1.0", "6", "1.06", "7", "19", "1.19", "20", "1.20", "21", "1.21
Example order API Private Order:
POST: https://test.billink.nl/api/order or https://client.billink.nl/api/order 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>order</ACTION>
		<TYPE>p</TYPE>
		<WORKFLOWNUMBER>1</WORKFLOWNUMBER>
		<ORDERNUMBER>1234567</ORDERNUMBER>
		<DATE>DD-MM-YYYY</DATE>
		<FIRSTNAME>Test</FIRSTNAME>
		<LASTNAME>Test</LASTNAME>
		<SEX>O</SEX>
		<INITIALS>T</INITIALS>
		<STREET>Wilhelminakade</STREET>
		<HOUSENUMBER>159</HOUSENUMBER>
		<HOUSEEXTENSION>A</HOUSEEXTENSION>
		<POSTALCODE>3072AP</POSTALCODE>
		<CITY>Rotterdam</CITY>
		<COUNTRYCODE>NL</COUNTRYCODE>
		<PHONENUMBER>0104141473</PHONENUMBER>
		<BIRTHDATE>01-01-1985</BIRTHDATE>
		<EMAIL>[email protected]</EMAIL>
		<EMAIL2>[email protected]</EMAIL2>
		<IP>172.2.168.1</IP>
		<DELIVERYSTEET>Wilhelminakade</DELIVERYSTEET>
		<DELIVERYHOUSENUMBER>159</DELIVERYHOUSENUMBER>
		<DELIVERYHOUSEEXTENSION>B</DELIVERYHOUSEEXTENSION>
		<DELIVERYPOSTALCODE>3072AP</DELIVERYPOSTALCODE>
		<DELIVERYCITY>Rotterdam</DELIVERYCITY>
		<DELIVERYCOUNTRYCODE>NL</DELIVERYCOUNTRYCODE>
		<ADITIONALTEXT>Toegevoegde tekst 1</ADITIONALTEXT>
		<TRACKANDTRACE>JVL1123457488</TRACKANDTRACE>
		<VATNUMBER>NL1234578B01</VATNUMBER>
		<CHECKUUID>XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</CHECKUUID>
		<CURRENCY>EUR</CURRENCY>
		<ORDERITEMS>
			<ITEM>
				<CODE>001</CODE>
				<DESCRIPTION>Test product 1</DESCRIPTION>
				<ORDERQUANTITY>1</ORDERQUANTITY>
				<PRICEINCL>9.95</PRICEINCL>
				<BTW>21</BTW>
			</ITEM>
			<ITEM>
				<CODE>002</CODE>
				<DESCRIPTION>Korting</DESCRIPTION>
				<ORDERQUANTITY>1</ORDERQUANTITY>
				<PRICEINCL>-0.95</PRICEINCL>
				<BTW>21</BTW>
			</ITEM>
		</ORDERITEMS>
	</API>
Example Order API Business Order:
POST: https://test.billink.nl/api/order or https://client.billink.nl/api/order 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>order</ACTION>
		<TYPE>b</TYPE>
		<WORKFLOWNUMBER>1</WORKFLOWNUMBER>
		<ORDERNUMBER>123456</ORDERNUMBER>
		<DATE>DD-MM-YYYY</DATE>
		<FIRSTNAME>Test</FIRSTNAME>
		<LASTNAME>Test</LASTNAME>
		<INITIALS>T</INITIALS>
		<STREET>Wilhelminakade</STREET>
		<HOUSENUMBER>159</HOUSENUMBER>
		<HOUSEEXTENSION>A</HOUSEEXTENSION>
		<POSTALCODE>3072AP</POSTALCODE>
		<CITY>Rotterdam</CITY>
		<COUNTRYCODE>NL</COUNTRYCODE>
		<PHONENUMBER>0104141473</PHONENUMBER>
		<COMPANYNAME>Billink B.V.</COMPANYNAME>
		<CHAMBEROFCOMMERCE>12345678</CHAMBEROFCOMMERCE>
		<EMAIL>[email protected]</EMAIL>
		<EMAIL2>[email protected]</EMAIL2>
		<IP>172.2.168.1</IP>
		<DELIVERYSTEET>Wilhelminakade</DELIVERYSTEET>
		<DELIVERYHOUSENUMBER>159</DELIVERYHOUSENUMBER>
		<DELIVERYHOUSEEXTENSION>B</DELIVERYHOUSEEXTENSION>
		<DELIVERYPOSTALCODE>3072AP</DELIVERYPOSTALCODE>
		<DELIVERYCITY>Rotterdam</DELIVERYCITY>
		<DELIVERYCOUNTRYCODE>NL</DELIVERYCOUNTRYCODE>
		<ADITIONALTEXT>Toegevoegde tekst 1</ADITIONALTEXT>
		<TRACKANDTRACE>JVL1123457488</TRACKANDTRACE>
		<VATNUMBER>NL1234578B01</VATNUMBER>
		<CHECKUUID>XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</CHECKUUID>
		<CURRENCY>EUR</CURRENCY>
		<ORDERITEMS>
			<ITEM>
				<CODE>001</CODE>
				<DESCRIPTION>Test product 1</DESCRIPTION>
				<ORDERQUANTITY>1</ORDERQUANTITY>
				<PRICEEXCL>8.2231</PRICEEXCL>
				<BTW>21</BTW>
			</ITEM>
			<ITEM>
				<CODE>002</CODE>
				<DESCRIPTION>Korting</DESCRIPTION>
				<ORDERQUANTITY>1</ORDERQUANTITY>
				<PRICEEXCL>-0.7851</PRICEEXCL>
				<BTW>21</BTW>
			</ITEM>
		</ORDERITEMS>
	</API>

For business orders it can be set that we accept price including VAT on the API. Please contact our customer service via [email protected] or via 010 - 414 14 73

Example Response approval:

	<API>
		<RESULT>MSG</RESULT>
		<MSG>
			<CODE>200</CODE>
			<DESCRIPTION>Order successfully added</DESCRIPTION>
		</MSG>
	</API>
Example Response error code:

	<API>
		<RESULT>MSG</RESULT>
		<MSG>
			<CODE>447</CODE>
			<DESCRIPTION>Missing check request uuid</DESCRIPTION>
		</MSG>
	</API>

It can prevent an order from being rejected. In most cases this is caused by our fraud filter. In this situation, a consumer must still be rejected. In addition, it may happen that data can be incomplete. We then provide an error code that can be found here.

Credit API

With the credit API a product or amount can be credited to the invoice. This API is optional.

For the credit API we need the following values:
VERSION In all cases this is "Billink2.0"
CLIENTUSERNAME Your Billink Username
CLIENTID Your unique API key
ACTION In all cases this is "credit"
INVOICENUMBER Invoicenumber which is used in the order API
CREDITAMOUNT Amount what must be credited including VAT
DESCRIPTION Explanation of the credit
Example Credit API:
POST: https://test.billink.nl/api/credit or https://client.billink.nl/api/credit 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>credit</ACTION>
		<INVOICES>
			<ITEM>
				<INVOICENUMBER>123456</INVOICENUMBER>
				<CREDITAMOUNT>10.95</CREDITAMOUNT>
				<DESCRIPTION>Test credit</DESCRIPTION>
			</ITEM>
		</INVOICES>
	</API>
Example Response with successful credit:

	<API>
		<RESULT>MSG</RESULT>
		<MSG>
			<STATUSES>
				<ITEM>
					<INVOICENUMBER>123456</INVOICENUMBER>
					<MESSAGE>Credit applied: 10.95 EURO.; Order paid.</MESSAGE>
					<CODE>200</CODE>
				</ITEM>
			</STATUSES>
		</MSG>
	</API>

It can happen that an error occurs during crediting. Read more about error codes and how you can solve them.

Start Workflow API

With the start workflow API, orders can be started as soon as these are delivered. An automatic starting delay of 3 days is set by default. When you want to use this API, we advise you to contact our customer service to turn off the automatic starting delay. This API is optional.

For the start workflow API we need the following values:
VERSION In all cases this is "Billink2.0"
CLIENTUSERNAME Your Billink Username
CLIENTID Your unique API key
ACTION In all cases this is "Activate Order"
WORKFLOWNUMBER Workflow number which is used in the order API
INVOICENUMBER Invoicenumber which is used in the order API
TRACKANDTRACE Track and trace code when available
Example Start Workflow API:
POST: https://test.billink.nl/api/start-workflow or https://client.billink.nl/api/start-workflow 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>activate order</ACTION>
		<INVOICES>
			<ITEM>
				<INVOICENUMBER>123456</INVOICENUMBER>
				<WORKFLOWNUMBER>1</WORKFLOWNUMBER>
				<TRACKANDTRACE>3SHEM123456789</TRACKANDTRACE>
			</ITEM>
		</INVOICES>
	</API>
Sample Response:

	<API>
		<RESULT>MSG</RESULT>
		<MSG>
			<CODE>500</CODE>
			<STATUSES>
				<ITEM>
					<INVOICENUMBER>123456</INVOICENUMBER>
					<MESSAGE>Success</MESSAGE>
					<CODE>500</CODE>
				</ITEM>
			</STATUSES>
		</MSG>
	</API>

Pay attention! This API can be used 1 minute after posting the order.
Read more about error codes and how you can solve them.

On Hold API

With the ON HOLD API, invoices can be put on hold for two weeks. This API is optional.

For the ON HOLD API we need the following values:
VERSION In all cases this is "Billink2.0"
CLIENTUSERNAME Your Billink Username
CLIENTID Your unique API key
ACTION In all cases this is "ON-HOLD"
INVOICENUMBER Invoicenumber which is used in the order API
WORKFLOWNUMBER Workflow number which is used in the order API
DAYS Number of days that the invoice must be placed on hold (max 14)
Example ON HOLD API:
POST: https://test.billink.nl/api/on-hold or https://client.billink.nl/api/on-hold 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>on-hold</ACTION>
		<INVOICENUMBER>123456</INVOICENUMBER>
		<WORKFLOWNUMBER>1</WORKFLOWNUMBER>
		<DAYS>14</DAYS>
	</API>
Sample Response:

	<API>
		<RESULT>MSG</RESULT>
		<MSG>
			<CODE>500</CODE>
			<DESCRIPTION>Order successfully set on hold till 2021-05-05</DESCRIPTION>
		</MSG>
	</API>

Read more about error codes and how you can solve them.

Payment API

With the Payment API, a payment can be booked on the invoice. These API can be useful if consumers regularly transfer amounts to the webshop. This API is optional.

For the payment API we need the following values:
VERSION In all cases this is "Billink2.0"
CLIENTUSERNAME Your Billink Username
CLIENTID Your unique API key
ACTION In all cases this is "payment"
INVOICENUMBER Invoicenumber which is used in the order API
AMOUNT The amount that must be booked
DESCRIPTION Description with payment
Example Payment API:
POST: https://test.billink.nl/api/payment or https://client.billink.nl/api/payment 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>payment</ACTION>
		<INVOICENUMBER>123456</INVOICENUMBER>
		<AMOUNT>10.95</AMOUNT>
		<DESCRIPTION>Betaling van de klant naar ons</DESCRIPTION>
	</API>
Sample Response:


	<API>
		<RESULT>MSG</RESULT>
		<MSG>
			<INVOICES>
				<ITEM>
					<INVOICENUMBER>123456</INVOICENUMBER>
					<MESSAGE>Success</MESSAGE>
					<CODE>500</CODE>
				</ITEM>
			</INVOICES>
		</MSG>
	</API>

Read more about error codes and how you can solve them.

Status API

The API status can be requested to see if an order is paid or not. This API is optional.

For the API status we need the following values:
VERSION In all cases this is "Billink2.0"
CLIENTUSERNAME Your Billink Username
CLIENTID Your unique API key
ACTION In all cases this is "status"
INVOICENUMBER Invoicenumber which is used in the order API
WORKFLOWNUMBER Workflow number which is used in the order API
Example Status API:
POST: https://test.billink.nl/api/status or https://client.billink.nl/api/status 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>status</ACTION>
		<INVOICES>
			<ITEM>
				<INVOICENUMBER>123456</INVOICENUMBER>
				<WORKFLOWNUMBER>1</WORKFLOWNUMBER>
			</ITEM>
		</INVOICES>
	</API>
Sample Response:

	<API>
		<RESULT>MSG</RESULT>
		<MSG>
			<CODE>200</CODE>
			<INVOICES>
				<INVOICE>
					<INVOICENUMBER>123456</INVOICENUMBER>
					<STATUS>1</STATUS>
					<DESCRIPTION>FACTUUR</DESCRIPTION>
				</INVOICE>
			</INVOICES>
		</MSG>
	</API>
Explanation different codes:
-1 Invoice not found
0 Not yet paid
1 Paid

Message API

With the Message API, messages can be placed on an order. These messages can be found in the backend of Billink by our customer service. This API is optional.

For the Message API we need the following values:
VERSION In all cases this is "Billink2.0"
CLIENTUSERNAME Your Billink Username
CLIENTID Your unique API key
ACTION In all cases this is "Message"
WORKFLOWNUMBER Workflow number which is used in the order API
INVOICENUMBER Invoicenumber which is used in the order API
MESSAGE The message that needs to be added
Example Message API:
POST: https://test.billink.nl/api/message or https://client.billink.nl/api/message 

	<API>
		<VERSION>BILLINK2.0</VERSION>
		<CLIENTUSERNAME>usertest</CLIENTUSERNAME>
		<CLIENTID>d38a3439590889df026367bf01d621e687b8d278</CLIENTID>
		<ACTION>message</ACTION>
		<WORKFLOWNUMBER>1</WORKFLOWNUMBER>
		<INVOICENUMBER>123456</INVOICENUMBER>
		<MESSAGE>Bericht voor administratie</MESSAGE>
	</API>
Sample Response:

	<API>
		<RESULT>SUCCESS</RESULT>
		<MSG>
			<CODE>500</CODE>
			<DESCRIPTION>Bericht toegevoegd</DESCRIPTION>
		</MSG>
	</API>

FAQ

Error codes

Per API we explain the different error codes and how you can solve it.

Check API:
001 Version is not correct, use "Billink2.0.
101 The username or the UID is incorrect.
102 The username or the UID is incorrect.
103 The promotion is unknown.
104 Workflow number is missing.
105 Worfklown number is not correct.
402 Incorrect phone number.
406 No type entered.
407 Incorrect type.
408 Company name is missing.
410 Last name is missing.
411 KVK number is missing.
412 First name is missing.
414 House number is missing.
415 Postcode is missing.
416 Wrong Postal Code format.
417 Phone number is missing.
418 Wrong formatting date of birth.
419 Missing email address.
420 Wrong email address.
421 Date of birth is missing.
422 Minimum age for orders via Billink is 16 years.
424 Wrong house number formatting.
425 Delivery address: Wrong house number formatting.
426 Delivery address not allowed.
427 Order amount is missing.
428 Order amount too high.
429 Order amount is larger than permitted.
430 Company name must be between 2 and 50 characters long.
431 House number Extension must be between 0 and 10 characters long.
435 Fraud risk too high.
500 Consumer has been approved.
501 Consumer has been rejected.
601 Check Structure XML.
603 Check Structure XML.
607 The username or the UID is incorrect.


Order API:
001 Version is not correct, use "Billink2.0".
101 The username or the UID is incorrect.
102 The username or the UID is incorrect.
103 The promotion is unknown.
401 Workflow number is missing.
402 Worfklow number is incorrect.
403 Invoice number already exists.
405 Date missing.
406 No type entered.
407 Incorrect type.
408 Company name is missing.
409 First name is missing.
410 Last name is missing.
411 Sex is missing.
412 Wrong formatting gender.
413 Street is missing.
414 House number is missing.
415 Postcode is missing.
416 City is missing.
417 Phone number is missing.
418 Missing email address.
419 Residence may only contain letters, spaces and 'characters.
420 Incorrect country code, use ISO 3166.
421 Date of birth is missing.
422 Wrong layout IP address.
427 KVK number is missing.
428 Item code is too long.
429 Wrong formatting KVK number.Must be between 5 and 25 characters.
430 Wrong formatting VAT number.
431 Wrong formatting VAT number.
432 Wrong email address.
433 Wrong layout second email address.
434 Invoice number does not meet the requirements (alphanumeric, _ and - are permitted).
440 CHECK-UUID is not correct, perform a new check api.
444 Order amount is higher than applied for in the CHECK API.
445 CHECK-UUID has expired, perform a new check api.
446 CHECK-UUID has already been used, perform a new check api.
447 CHECK-UUID is missing.
448 Company name must be between 2 and 50 characters long.
449 Telephone number may only contain numbers.
450 House number Extension must be between 0 and 10 characters long.
451 workflowWithoutGuaranteeIsUsedForCheckRequest
452 Amount is higher than agreed.
501 Order has been refused on the basis of fraud.
601 Check Structure XML.
603 Check Structure XML.
607 The username or the UID is incorrect.


Credit API:
001 Version is not correct, use "Billink2.0".
101 The username or the UID is incorrect.
102 The username or the UID is incorrect.
103 The promotion is unknown.
402 Worfklown number is not correct.
403 Invoice number already exists.
601 Check Structure XML.
603 Check Structure XML.
607 The username or the UID is incorrect.
705 Invoice is missing.
706 Invoice not found.
707 Credit cannot be performed in this phase.
708 Credit cannot be carried out.Try again later.


Start Workflow API:
001 Version is not correct, use "Billink2.0".
101 The username or the UID is incorrect.
102 The username or the UID is incorrect.
103 The promotion is unknown.
603 Check Structure XML.
607 The username or the UID is incorrect.
705 Invoice is missing.
706 Invoice not found.
707 Credit cannot be performed in this phase.
708 Credit cannot be carried out.Try again later.


On Hold API:
001 Version is not correct, use "Billink2.0".
101 The username or the UID is incorrect.
102 The username or the UID is incorrect.
103 The promotion is unknown.
401 Invoice number is missing.
402 Invoice number incorrect.
403 Period is too long.Maximum 14 days.
603 Check Structure XML.
607 The username or the UID is incorrect.
701 Order cannot be placed on hold.


Payment API:
001 Version is not correct, use "Billink2.0".
101 The username or the UID is incorrect.
102 The username or the UID is incorrect.
103 The promotion is unknown.
402 Workflow number is unknown.
420 Invoice number is missing.
603 Check Structure XML.
607 The username or the UID is incorrect.
701 Order cannot be placed on hold.
704 Invoice number unknown.
706 No payment can be booked on this invoice.
707 Order has already been paid.
708 Description is too long.Maximum 30 characters.

Contact

We look forward to a successful collaboration. If you don't understand our integration completely, we are happy to help you. This is possible on workdays from 8:30 a.m. to 5 p.m. [email protected] or via 010 - 414 14 73