API Stopped work

Extensibility
1

API stopped to work for us.

Did something happened between yesterday and today? No changes on our code have been made.

Thanks.

2

The output I have is.

1Cannot load the schema for the namespace ‘http://www.QuickFile.co.uk’ - The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. 1Could not find schema information for the element ‘http://www.QuickFile.co.uk:Invoice_Search’. 2Could not find schema information for the element ‘http://www.QuickFile.co.uk:Header’. 3Could not find schema information for the element ‘http://www.QuickFile.co.uk:MessageType’. 4Could not find schema information for the element ‘http://www.QuickFile.co.uk:SubmissionNumber’. 5Could not find schema information for the element ‘http://www.QuickFile.co.uk:Authentication’. 6Could not find schema information for the element ‘http://www.QuickFile.co.uk:AccNumber’. 7Could not find schema information for the element ‘http://www.QuickFile.co.uk:MD5Value’. 8Could not find schema information for the element ‘http://www.QuickFile.co.uk:ApplicationID’. 11Could not find schema information for the element ‘http://www.QuickFile.co.uk:Body’. 12Could not find schema information for the element ‘http://www.QuickFile.co.uk:SearchParameters’. 13Could not find schema information for the element ‘http://www.QuickFile.co.uk:ReturnCount’. 14Could not find schema information for the element ‘http://www.QuickFile.co.uk:Offset’. 15Could not find schema information for the element ‘http://www.QuickFile.co.uk:OrderResultsBy’. 16Could not find schema information for the element ‘http://www.QuickFile.co.uk:OrderDirection’. 17Could not find schema information for the element ‘http://www.QuickFile.co.uk:InvoiceType’. 18Could not find schema information for the element ‘http://www.QuickFile.co.uk:ShowDeleted’. 19Could not find schema information for the element ‘http://www.QuickFile.co.uk:InvoiceNumber’. 20Could not find schema information for the element ‘http://www.QuickFile.co.uk:Status’.

3

Hello @APereira

I’ve asked a developer to look into this. Bear with me - I’ll come back to you as soon as I’ve had a response.

[Update]
@APereira - This should now be working as expected. Please let me know if you encounter any further issues.

4

Thank you very much :slight_smile:

1 Like
5

@QFMathew

Yes it is :slight_smile:

Any change on your side?

6

I apologise, it was an internal routing problem in our network.

There are no changes on our side that you need to worry about.

1 Like