HELP & Documents


Date: 2016.7.22        Author: SysAdmin

Search index: (title and article description search)

No record was found!


Authorization API

Used by WEBDO.COM (DO) web-services it offers also the possibility to create authorization services for your applications using RESTful API's.

Here are the public API's.

1. OPEN authorization using an WEBDO.COM user account.

2. Create/verify CAPTHCA

3. Maintain users list

Using DO authorization allows fast implementation of your projects solving users basic management (authorization, change password).

1. Open authorization

Open authorization let you authorize an user of your web application using the credits, this option allow you to easily create an application that require authorization without all the hassle to maintain and secure an authorization mechanism (authorization, password change/recovery ...).

You may authorize all users just receiving the information that the username is valid and passed the login or you can keep a simple list of your users and validate access requests with open authorization.

1.1. Authorization request

From your web application open next link:<auth request string>


<auth request string>
is a base64 of
{"a":"<return url>","b":"<request codes>","c":"<app code>"}

return url : provided URL to return to after credential validation.

request codes: a string that instruct the authorization engine what to deliver back

            e: email
            t:  token
            u: username
            f: firstname
            l: lastname

app code: application code, your application should be registered with here 


token: If your web application requires access to the user CLOUD storage to store files or structured information (JSON,XML,...) this token will provide access to a restricted area available only for the web application with defined <app code>. Files are stored under "Applications/<folder name>/ in user CLOUD at

The authorization web page will return to the <return url> providing a base64 of response into the url hash.

Response sample:

You may use Javascript to read the string like:


var s = window.location.hash.replace('#','');
var d = JSON.parse(s);


Returned json is:

{a:"ok", e:<email>, t:<token>, u:<username>, f:<firstname>, l:<lastname>}  according with described "request codes".

or {a:"nok"} for an invalid user password or CANCEL action.

2. Create/verify CAPTHCA

This API is free to be used in any project you may have.

Captcha API allows creation of a "captcha" simple image that uses a 4 characters code. While is not the most modern approach is effective and simple to implement, being also easy to be used.

It uses A-Z characters, gradient colors and colored lines over text to create an image that can be read only by humans creating an effective barrier to automated processes.

The image is created server side and provided as data image along with some other parameters used later to verify the code. The method was tested against most advanced image recognition softwares.

2.1. Get image:

Method: GET


Return: JSON     {captch:<captcha>,key:<key>}

        Sample returned JSON:    {captcha:"data:image/png;base64,iV ...",key:"a0b2b715"}

The "captca" can be used as source for an "img" in your HTML code.

2.2 Verify captcha:

Method: POST

Url :

data: {key:<key>,code:<code>}

Return JSON:

on OK:

{"response":"code ok"}

on Error:

{"response":"invalid code1"}

always return http status code 200.

<code> is case sensitive, should be uppercase, it is wise to send it uppercase from your code to let your users enter any case.

Users list

Loading data

Loading WordBricks ...

| 1.1.1. Welcome| 1.1.2. Register a new account| 1.1.3. Start| 1.1.4. Technical support| 1.2.1. New website| 1.2.2. New page| 1.2.3. Sections / Page BLOCKS| 1.2.4. Settings| 1.2.5. Save / Backup / Restore| 1.2.6. Background| 1.2.7. My pages| 1.2.8. Page settings| 1.2.9. Website header| 1.2.10. Website menu| 1.2.11. Publish| 1.2.12. Compatibility| 1.2.13. Specials blocks| 1.2.14. DATABLOCKS| 1.2.15. Contacts Form| 1.2.16. Numbers Shuffle - Game| 1.2.17. ChatBox| 2.1.1. WEB hosting| 2.2.1. Hosting plans| 2.3.1. Domain Names| 2.3.2. Register a new domain name| 2.3.3. Domain name management| 2.3.4. Add a SSL certificate| 2.3.5. Create a SSL certificate| 2.3.6. Domain Name Redirects| 2.4.1. SEO informations| 3.1.1. DRIVE| 3.2.1. Files storage| 3.2.2. API drive access| 3.2.3. Safe share files| 3.3.1. WebDO IDE| 4.1.1. Email| 4.1.2. Email Services Names| 5.1.1. Databases| 5.1.2. API key| 5.2.1. Micro data| 5.3.1. Datasets (test fake data)| 6.1.1. We use SOA| 6.2.1. Authorization| 6.2.2. File access| 6.2.3. SendMail| 6.2.4. QR Code| 6.2.5. Document storage API| 6.2.6. MicroData API| 6.2.7. SQL API| 6.2.8. IP API| 6.2.9. DRIVE API| 6.2.10. Link Redirects API| 7.1.2. WebDo CLOUD| 7.1.3. Services Domains| 8.1.1. Payment| 8.1.2. European VAT| 8.2.1. Privacy policies| 8.2.2. Refund policies| 8.2.3. Change web hosting plan| 8.2.4. Minimum order value| 9.1.1. Terms and conditions| 10.1.2. About us| 10.1.2. | 11.1.3. Newsletter Application| 11.2.1. Dashboard| 11.2.2. Subscribers| 11.2.3. Campains| 11.2.4. Email Builder| 11.2.5. Forms| 11.2.6. Forms Builder| 11.2.7. Subscribers Management| 11.2.8. Integrate a custom subscription form using webdo website builder| 12.1.1. Survey Application| 12.2.1. Dashboard| 12.2.2. Add/Edit survey| 12.2.3. Settings| 12.2.4. Campaigns| 12.2.5. Reports| 12.2.6. Survey preview| 12.2.7. Page jumps| 12.2.8. Question types| 13.1.1. E-Detailing Application| 13.2.1. Dashboard| 13.2.2. Presentations| 13.2.3. Campaigns| 13.2.4. Reports| 13.2.5. Templates|