Download the PHP package always-open/oxylabs-api without Composer
On this page you can find all versions of the php package always-open/oxylabs-api. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download always-open/oxylabs-api
More information about always-open/oxylabs-api
Files in always-open/oxylabs-api
Package oxylabs-api
Short Description Package to integrate with Oxylabs APIs
License MIT
Homepage https://github.com/always-open/oxylabs-api
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package oxylabs-api
This is my package oxylabs-api
This is where your description should go. Limit it to a paragraph or two. Consider adding a small example.
Support us
We invest a lot of resources into creating best in class open source packages. You can support us by buying one of our paid products.
We highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using. You'll find our address on our contact page. We publish all received postcards on our virtual postcard wall.
Installation
You can install the package via composer:
You can publish and run the migrations with:
You can publish the config file with:
This is the contents of the published config file:
Optionally, you can publish the views using
Usage
Parse status
parse_status_code is a field of a response the Oxylabs parser actually produced, not of every
Oxylabs response. When the parser never ran - bot-check / CAPTCHA / error-page classes, unsupported
page types, raw type=html retrievals - Oxylabs omits the key entirely. The content DTOs therefore
type it as ?int, and getParseStatusCode() distinguishes three states:
| state | parse_status_code |
hasParseStatus() |
getParseStatusCode() |
|---|---|---|---|
| vendor reported a status we model | e.g. 12000 |
true |
that case, e.g. ParseStatus::SUCCESS |
| vendor reported a status we do not model yet | e.g. 12001 |
true |
ParseStatus::UNKNOWN |
| vendor reported no status at all | null |
false |
ParseStatus::NOT_REPORTED |
ParseStatus::NOT_REPORTED is a local sentinel (0) deliberately outside the vendor's 120xx
numbering space - it is never a code Oxylabs sent.
A NOT_REPORTED status means every other field on that content object is untrustworthy. Guard on
$content->success() or $content->hasParseStatus(), never on instanceof (now satisfied by an
all-null object) and never on empty() (always false for an object).
Testing
Changelog
Please see CHANGELOG for more information on what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Security Vulnerabilities
Please review our security policy on how to report security vulnerabilities.
Credits
- Quentin Schmick
- All Contributors
License
The MIT License (MIT). Please see License File for more information.
All versions of oxylabs-api with dependencies
always-open/laravel-request-logger Version ^3.0|^4.0
illuminate/contracts Version ^12.0||^13.0
spatie/laravel-data Version ~4.16
spatie/laravel-package-tools Version ^1.16
ext-dom Version *
ext-libxml Version *