PHPackages                             fourkitchens/picsart-api-client - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [API Development](/categories/api)
4. /
5. fourkitchens/picsart-api-client

ActiveLibrary[API Development](/categories/api)

fourkitchens/picsart-api-client
===============================

01PHP

Since May 9Pushed 3y ago11 watchersCompare

[ Source](https://github.com/fourkitchens/picsart-api-client)[ Packagist](https://packagist.org/packages/fourkitchens/picsart-api-client)[ RSS](/packages/fourkitchens-picsart-api-client/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

SwaggerClient-php
=================

[](#swaggerclient-php)

Introduction
------------

[](#introduction)

Picsart Image Tools API is a simple HTTP interface. The results are usually the URL of the output image. To get started, first you need to [get your API Key](https://picsart.io/accounts/login). Below you can find the sample codes to get started easily. Reference docs are given with more information about available parameters that can be adjusted. ## Sample Run `curl -X POST \\ 'https://api.picsart.io/tools/1.0/removebg' \\ -H 'x-picsart-api-key: APIKEYHERE' \\ -F 'output_type=cutout' \\ -F 'image_url=https://cdn140.picsart.com/13902645939997000779.jpg'` ## Server The demo environment has been removed (). We recommend that you use the new production environment () instead. Please contact us if you find any issues. ## API Key To try out our services you will need to \* [create an account](https://picsart.io/accounts/login), \* create an app under [My Apps](https://picsart.io/my-apps/) \* and get the API key required for authorization. You can find more details about this process in the [Quickstart](https://picsart.io/api-quickstart). ## Input File Input images of type JPG, PNG and WEBP are supported. Input image file size is 100 MB max. References to uploaded image files will be valid and can be used within 24 hours. ## Output Formats You can request one of three formats, JPG, PNG, WEBP, via the format parameter. The result files will be available for use for 24 hours. ## Rate Limit Users can process up to 100 requests per month during the demo run. When the rate limit is hit, the API will return 429 code with the info: `     {        \"fault\": {          \"faultstring\": \"Rate limit quota violation. Quota limit  exceeded. Identifier : _default\",           \"detail\": {             \"errorcode\": \"policies.ratelimit.QuotaViolation\"           }         }      }        ` ## Authentication Authentication should be done via the provided API Key. API Key can be sent as a header: ` curl 'https://api.picsart.io/tools/1.0/effects' -H 'x-picsart-api-key: APIKEY' ` [Developer Guidelines](https://picsart.io/terms)

This PHP package is automatically generated by the [Swagger Codegen](https://github.com/swagger-api/swagger-codegen) project:

- API version: 2.0
- Build package: io.swagger.codegen.v3.generators.php.PhpClientCodegen

Requirements
------------

[](#requirements)

PHP 5.5 and later

Installation &amp; Usage
------------------------

[](#installation--usage)

### Composer

[](#composer)

To install the bindings via [Composer](http://getcomposer.org/), add the following to `composer.json`:

```
{
  "repositories": [
    {
      "type": "git",
      "url": "https://github.com/git_user_id/git_repo_id.git"
    }
  ],
  "require": {
    "git_user_id/git_repo_id": "*@dev"
  }
}

```

Then run `composer install`

### Manual Installation

[](#manual-installation)

Download the files and include `autoload.php`:

```
    require_once('/path/to/SwaggerClient-php/vendor/autoload.php');
```

Tests
-----

[](#tests)

To run the unit tests:

```
composer install
./vendor/bin/phpunit

```

Getting Started
---------------

[](#getting-started)

Please follow the [installation procedure](#installation--usage) and then run the following:

```
