An unofficial REST API for PhpBB with example client.
- PhpBB extension: GPLv2
- Example client: MIT
Project is provided as-is. It was built to support a particular website and will not see regular updates. If you want to try to add this to the PhpBB extension database, add new features, or fix integration with future versions of PhpBB, please feel free to clone the repo and do with it as you please.
- Single sign-on with PhpBB
- Auth integration with sites not written in PHP.
- Avoid conflicts when PhpBB and the integrated site use different versions of Symfony components.
- It is not a replacement for whatever PhpBB ultimately releases for their REST API. It is just a workaround until PhpBB releases something that can allow for integrating with their auth system more cleanly.
- It does not try to do more than was needed for the website I help with:
- It is currently meant to be accessed via https from a client on the same server, and so some security features that you find in some public apis may be missing.
- It doesn't alter the way authentication works. It mearly exposes PhpBB's existing cookie-based auth system via a json interface.
- It does not try to qualify for upload to the PhpBB extension database. I did my best to to adhere to the extension guidelines, but in the end there are some issues I couldn't avoid such as "15. login_forum_box() or login_box() is used for login." for obvious reasons.
- None at this time, but there are likely some which exist.
Extension:
- Install the extension as you would any other extension.
Example client:
- Copy the client files to a directory on your server
- Install composer
- Use composer to download the GuzzleHttp dependency
- Command will look something like "php composer.phar install" and needs to be run from the directory with the composer.json file.
The root path of the API will be: https://<hostname><forum path>/app.php/restApiV1/ If you have url rewriting enabled (in General->Server Settings of the control panel) and working for your forum, the path can be shortened to https://<hostname><forum path>/restApiV1/
NOTE: Due to PhpBB's cookie based auth, you will need to handle cookies passed to and returned by the api. You shouldn't directly store these. Your client should act as a proxy for these cookies. I recommend looking at the example client and reusing the code if you are working with PHP on the client side.
Request
Request Property | Value |
---|---|
method | POST |
url | <apiRoot>/login |
Parameters | Current cookies and the following form parameters in the POST body:
|
Response
401 status code on auth failure, otherwise user data json for logged in user. (See current user API)
Request
Request Property | Value |
---|---|
method | POST |
url | <apiRoot>/logout |
parameters | Current cookies |
Response
User data json for anonymous user. (See current user API)
Request
Request Property | Value |
---|---|
method | GET |
url | <apiRoot>/users/me |
parameters | Current cookies |
Resonse
Received cookies should be proxied to browser
JSON:
{
"isRegistered":true,
"isBanned":true,
"isPasswordChangeNeeded":true,
"userId":15,
"userName":"Banned"
}
Field | Value |
---|---|
isRegistered | Will be true if the user is logged in. |
isBanned | True if user is banned from forum. |
isPasswordChangeNeeded | If true, you should notify or redirect user to the forum's user control panel so they can change their password. |
userId | The user's forum id |
userName | The user's user name. |