Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Web services: Difference between revisions

From MoodleDocs
(Cleaned up and added an actual listing of our web services!)
(36 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{Moodle_2.0}}
=== How it works ===
 
This example will give you an idea of how our web services infrastructure works.  
==Introduction==
#The client sends a username and password to the web service login script.
This page describes the Web Services implementation that was added to Moodle 2.0 and is being extended with every subsequent version.
#The script returns a token for that user account.
 
#The client calls a particular web service function on a protocol server including the token .
We support multiple web service protocols (REST, SOAP, XML-RPC and AMF). If that's not enough, support for new protocols can be added easily.
#The protocol server uses the token to check that the user can call the function.
 
#The protocol server calls the matching external function, located under the \component\external namespace (previously in a externallib.php file inside the relevant module).
 
== How it works ==
This simple example will give you an idea of how our web services infrastructure works.  See [[External services security]] for more details.
#The client sends a username and password to the web service protocol server script.
#The protocol server returns a session token for that user account (how this is sent depends on the protocol).
#The client calls a particular web service function including the session token.
#The protocol server uses the token to check that the web service session is still active.
#The protocol server call the matching external function, located in a externallib.php file inside the relevant module.
#The external function checks that the current user has_capability to do this operation.
#The external function checks that the current user has_capability to do this operation.
#The external function calls the matching Moodle core function (in lib.php usually).
#The external function calls the matching Moodle core function (in lib.php usually).
Line 20: Line 12:
#The protocol server returns the result to the client.
#The protocol server returns the result to the client.


==Web description format==
== Developer documentation==
 
The full API can be found on any Moodle sites under ''' Administration block > Plugins > Web services > API Documentation'''.
All functions that can be called via web services are declared in a db/service.php file and can be defined in an externallib.php file somewhere.  The classes we use to define these functions are explained in the [https://docs.moodle.org/en/Development:Web_services_description External Service description document].
 
==Web services functions==
 
Every Moodle sites can provide you with a page listing all function descriptions, with useful advice for any supported protocol.
 
To call this page: ''your_moodle/webservice/wsdoc.php?protocol=soap
''
 
However, here is a list of the functions available in Moodle 2.1:
 
user:
* create_users()
* delete_users()
* update_users()
* get_users_by_id()
* get_course_participants_by_id()
* get_users_by_courseid()
 
course:
* get_courses()
* create_courses()
 
group:
* create_groups()
* get_groups()
* get_course_groups()
* delete_groups()
* get_groupmembers()
* add_groupmembers()
* delete_groupmembers()
 
enrol:
* get_enrolled_users()
* get_users_courses()
* role_assign()
* role_unassign()
 
enrol/manual:
* manual_enrol_users()
 
webservice:
* get_siteinfo_parameters()
 
message:
* send_instantmessages()
 
files:
* get_files()
* upload()


'''Note:''' Additional services are available for uploading and downloading files which are not in the API Documentation - they are accessed in a different way. See [[Web services files handling]]


* [[How to contribute a web service function to core]]
* [[Adding a web service to a plugin| Adding a web service to your plugin]]
* Code example: [https://gist.github.com/timhunt/51987ad386faca61fe013904c242e9b4 Adding a web service, using APIs] by (Tim Hunt)
* [[Creating a web service client | Implement a web service client]]
* [[Web services files handling]]
* [[Web_services_Roadmap | Web service Listing & Roadmap]]


==Authentication==
== Specification and brainstorming ==
Please have a look to the [[External services security]] page
* [[External services security | External services security]]
* [[External services description | External services description]]


==See also==
== See also ==
* The official discussion [http://moodle.org/mod/forum/view.php?id=6971| forum is here]
* [[Web_service_API_functions|Web service API functions]]
* The tracker issues are here: MDL-12886 and MDL-17135
* [[:en:Web_services_FAQ|Web services FAQ]]
* [[External services security]]
* [[:en:How_to_create_and_enable_a_web_service|How to create and enable a web service]]
* [[External services description]]
* [[:en:Enable mobile web services|How to enable the mobile web service]]
* [[Creating a web service and a web service function]]
* [[:en:Web_services|Web services user documentation]]
* [[Creating a web service client]]
* [http://www.slideshare.net/juanleyva/mastering-moodle-web-services-development Mastering Moodle Web Services development] - Last session of the Hackfest in the MoodleMoot UK 2016
* [[Web_Services]]


[[Category:Web Services]]
[[Category:Web_Services]]

Revision as of 17:47, 30 October 2020

How it works

This example will give you an idea of how our web services infrastructure works.

  1. The client sends a username and password to the web service login script.
  2. The script returns a token for that user account.
  3. The client calls a particular web service function on a protocol server including the token .
  4. The protocol server uses the token to check that the user can call the function.
  5. The protocol server calls the matching external function, located under the \component\external namespace (previously in a externallib.php file inside the relevant module).
  6. The external function checks that the current user has_capability to do this operation.
  7. The external function calls the matching Moodle core function (in lib.php usually).
  8. The core function can return a result to the external function.
  9. The external function will return a result to the protocol server.
  10. The protocol server returns the result to the client.

Developer documentation

The full API can be found on any Moodle sites under Administration block > Plugins > Web services > API Documentation.

Note: Additional services are available for uploading and downloading files which are not in the API Documentation - they are accessed in a different way. See Web services files handling

Specification and brainstorming

See also