Opening the add-on

Request body

{
"token": "" ,
"current_admin_language": "cs" ,
"version": 0,
"time": "",
"signature": "",
"signature_v2": ""
}
                                        

Response body

{
"url": "" ,
"type": "iframe"
}
                                            

Signature pattern

You can learn what a signature is and why it is used here.

signature_token is a special identifier for your add-on. You can find it in Marketplace / Add-on details - Add-on development (read more)

<?php

$data = implode(";", [
    "token" => "...",
    "time" => "...",
    "signature_token" => "...",
    ]);
$signature_v2 = 'a0e0a3e7689bd4c80e4d6ffcccb05235b864e1d0';
$signaturePublicKey = file_get_contents("https://files.upgates.com/addons/signature/api.signature.pub.key");
$verify = openssl_verify($data, base64_decode($signature_v2), $signaturePublicKey, OPENSSL_ALGO_SHA256);
            
        

Add-on not available

• Any response other than HTTP status code 200.
• The HTTP 200 response is not valid.

Iframe

• We need to get as close to the Upgates administration styles as possible.
• There will be no communication between the iframe and the Upgates administration.

Answer (Validation)

• cURL supported content encoding
  
  • libcurl
  • deflate
  • gzip
  • br
  • zstd

Changelog