API link has disconnected AGAIN

API link has disconnected AGAIN . This is getting beyond a joke...I am now yet again double selling because the link has disconnected again. I had to stop 30,000 sales only a few months ago whilst this was sorted out and now it has happened again. I will wait until 5pm GMT tomorrow for this to de sorted or I will have to end all my sales again...this is causing me a huge amount of work which I do not need to do so please sort this out IMMEDIATELY.

Hello richnoddystamps,

We have just checked your access keys and they are valid and operational.

"API link has disconnected AGAIN" what do you mean? You can no longer have a connection token or you get an error during a specific call?

Can you specify your problem in order to find an adequate solution ?

Kind Regards

I am not a computer specialist so I can only say what I see.

A lot of the items that have sold on Delcampe are still for sale on my own website. This has led to a number of double sales.

This item number for example..#1546545106 was sold on Delcampe on 26th July. It was not reported to my website as sold and has now been sold on my website on 4th August. This has been repeated across probably 60-70 items which I am now having to manually remove from my website.

I have this entry on my website which was built in by my webmaster, and which I activated late last night....
====================================
WARNING - ONLY USE THE LINKS BELOW IF YOU KNOW FOR SURE THAT THE NOTIVICATIONS HAVE STOPPED
It is not known (at present) what happens if you resend these requests while they are still working. It may switch them off.

Each of the links below provides a method to do what Paul did manually in the past !

1. Resend request for Delcampe New Notifications Here

2. Resend request for Delcampe Sold Notifications Here

3. Resend request for Delcampe Update Notifications Here

4. Resend request for Delcampe Close Notifications Here

5. Resend request for Delcampe Error Notifications Here

These links are provided with no guarantee, but will provide a server response, successful or otherwise.
========================================

1. Resend request for Delcampe New Notifications Here....................this is
===============================================
Response: 2022-08-05 09:05:01 item POST 400 Max number of notification by type reach
$VAR1 = bless( { '_protocol' => 'HTTP/1.1', '_content' => ' 2022-08-05 09:05:01 item POST 400 Max number of notification by type reach ', '_rc' => 200, '_headers' => bless( { 'connection' => 'close', 'cache-control' => 'max-age=0, must-revalidate, private', 'date' => 'Fri, 05 Aug 2022 09:05:01 GMT', 'vary' => 'Accept-Encoding', 'client-ssl-cert-issuer' => '/C=US/O=Let\'s Encrypt/CN=R3', 'client-ssl-cipher' => 'ECDHE-RSA-AES128-GCM-SHA256', 'client-peer' => '82.146.118.155:443', 'strict-transport-security' => 'max-age=15552000', 'client-date' => 'Fri, 05 Aug 2022 09:05:01 GMT', 'content-type' => 'text/xml; charset=UTF-8', 'client-transfer-encoding' => [ 'chunked' ], 'server' => 'nginx', 'client-ssl-socket-class' => 'IO::Socket::SSL', 'client-response-num' => 1, '::std_case' => { 'client-response-num' => 'Client-Response-Num', 'client-ssl-cert-issuer' => 'Client-SSL-Cert-Issuer', 'client-ssl-cipher' => 'Client-SSL-Cipher', 'client-peer' => 'Client-Peer', 'strict-transport-security' => 'Strict-Transport-Security', 'client-date' => 'Client-Date', 'x-frame-options' => 'X-Frame-Options', 'client-ssl-cert-subject' => 'Client-SSL-Cert-Subject', 'client-transfer-encoding' => 'Client-Transfer-Encoding', 'client-ssl-socket-class' => 'Client-SSL-Socket-Class' }, 'x-frame-options' => 'SAMEORIGIN', 'client-ssl-cert-subject' => '/CN=delcampe.net', 'expires' => 'Fri, 05 Aug 2022 09:05:01 GMT' }, 'HTTP::Headers' ), '_msg' => 'OK', '_request' => bless( { '_content' => 'destination=http%3A%2F%2Fwww.richnoddystamps.co.uk%2Fcgi-bin%2Fdelcampe%2Fdelcampe-new-notification.pl%3Ftoken%3Dnoddy¬ificationType=Curl_Seller_Item_Add', '_uri' => bless( do{\(my $o = ' Link (https) }, 'URI::https' ), '_headers' => bless( { 'user-agent' => 'libwww-perl/6.05', 'content-type' => 'application/x-www-form-urlencoded', 'content-length' => 156, '::std_case' => { 'if-ssl-cert-subject' => 'If-SSL-Cert-Subject' } }, 'HTTP::Headers' ), '_method' => 'POST', '_uri_canonical' => $VAR1->{'_request'}{'_uri'} }, 'HTTP::Request' ) }, 'HTTP::Response' );
================================================

Hello richnoddystamps,

As we can read in the return of the API call: "Max number of notification by type reach".

You cannot configure more than 5 notifications by type.
Ideally, you should have no more than one. While you currently have at least 3.
Here is the call to get your current notifications settings: Link (https)

And here the call to delete a specific notification:
Link (https)

As a reminder, here are the available types: Link (https) your-feedback-url

By the way, as you can read here: Link (https)
You can also use this type of notification (Email_Error_LimitReached) to be notified when a notification is disabled.

Currently, we have no problem on our side. I advise you to check with your developer how he uses our api because there are better ways to implement it to avoid the error you mention.

Kind Regards

I don't understand...this has been working for many years...why has this not been told to me before. Everything has worked perfectly.