vTiger with V18

[DaveA66]

Hi
Has anything changed with vTiger integration in V18?
It used to work OK, but now when doing a lookup, I get a 404 from the vTiger server.
I cannot be exactly sure the failure coincides with the upgrade to V18 but nothing else has changed that I am aware of.
The result I get is:-

Server returned a non successful status code - HTTPStatusCode=NotFound - Reason=Not Found - Content=<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta http-equiv="x-ua-compatible" content="ie=edge"> <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> <title>404 Not Found</title> <link rel="stylesheet" href="/error_docs/styles.css"> </head> <body> <div class="page"> <div class="main"> <h1>Server Error</h1> <div class="error-code">404</div> <h2>Page Not Found</h2> <p class="lead">This page either doesn't exist, or it moved somewhere else.</p> <hr/> <p>That's what you can do</p> <div class="help-actions"> <a href="javascript:location.reload();">Reload Page</a> <a href="javascript:history.back();">Back to Previous Page</a> <a href="/">Home Page</a> </div> </div> </div> </body> </html>

Any help appreciated!

Thanks

 

[Evolute IT]

The integration uses the REST API, and not the WebService anymore.

Have you enabled the new API?

 

[DaveA66]

No, I haven't - is this documented?

 

[Evolute IT]

No, I haven't - is this documented?

It's a VTiger thing. You need a recent version and the API enabled. Probably somewhere in your settings.

I've seen this a few times.

 

[DaveA66]

OK thanks!

We might be screwed then we have a customised open source version.
I'll take a look!

Cheers

 

[Evolute IT]

OK thanks!

We might be screwed then we have a customised open source version.
I'll take a look!

Cheers

Yeah those things happen lol

 

[edossantos]

The change from the Webservice API to the REST API was requested by Vtiger. We have been contacted by them informing us that we should update our template to use the REST API instead of the Webservice API, due to the following reasons:
1) With the REST API we will use basic authentication, instead of getting a session name. This reduces the number of requests sent to the API. Vtiger has a daily limit for API request, and some customers are exceeding it. By using the REST API the threshold would be much higher.
2) The Webservice API will be removed soon, so we should move to the REST API.

This was indeed introduced in v18 alpha (December 2020) as shown in the 3CX change log.