damonjones / vebra-php-api-wrapper Goto Github PK

The package no longer seems to be referenced on packagist could you please add it back on there to make installation simpler?

Thank you

attribute value 'featured' is always 1, even in fetched xml it is 0, i guess the error is in type casting of attribute type 'featured' as Boolean to int then it workd.

The title of the link to the API spec in the README file currently says version 3, but needs to be updated to reflect the recent changes from @thinkerytim .

@damonjones Can you update please?

Hello,

Any ideas why I may be receiving 401's intermittently? I'm working on my local machine, I have a .txt file that contains my token.

Most of the time, I can fetch data (branches, properties etc). However from time to time, an UnauthorizedException is thrown and I can't seem to use the Vebra API for a little while (haven't worked out if there's a time period I cant' fetch data).

I've read their documentation and can't find any reason why I'm getting this, like rate limiting etc.

Any help would be greatly appreciated!

does the API wrapper support decoding the "types" and "relatedtypes" data? (http://webservices.vebra.com/export/xsd/v8/rightmovetypes.xsd & http://webservices.vebra.com/export/xsd/v8/propertyrelatedtypes.xsd)

There's a bunch of different values, and instead of a straight 1 to 1 mapping they chose to make the propstatus value differ depending on other values in the feed.

This isn't your problem, but Vebra's webservices are really pretty terrible about reliability. Timeouts are extremely frequent, where the API won't return data in the default 5 seconds allowed by the buzz client.

You can edit the API.php construct method and add a line for $this->client->setTimeout(30); or whatever-- but even with a 30 second timeout they are not always reliable. If you ever feel the urge a method to retry would be welcome-- or maybe allow the timeout to be passed into the constructor.

Thanks!

How do you go about generating a token the first time you instantiate the API?

YDD\Vebra\TokenStorage\File attempts to load an existing token and throws an exception when it can't find one.

You have some logic to handle expired tokens in the API but not requesting one in the first place.

What did you intend to happen here?

Many thanks