ProBill API is an interface that allows third-party applications to communicate with theProBill.roplatform, regardless of the code in which they were written.
\n\nUsing ProBill API, third-party applications have the ability to perform most of the operations available onProBill.roCMS:
\n\nAll communication between the third-party application and the ProBill API will be performed in a secure environment, using the HTTPS protocol. Authentication is realised throughJSON Web Tokens. JWT authentication involves sending a verified username and password to login method. If the Auth is a success, you will receive a token that you'll need to include as a header in your requests to methods that require Authentication.
For example, if the login method returns \"token\": \"ab0dde18155a43ee83edba4a4542b973\" you will need to include the following header to your requests:
Note: in order to reduce the number of requests, please save and reuse JWT token until it expires. If the token isn’t valid (because, for example, the token has expired), the user will be sent an HTTP 401 Unauthorized header, and the script will exit. At that moment you can refresh the token.
\n\nAPI baseUrl is https://probill.ro/api/. Please use the https protocol directly to avoid unnecessary redirects.
ProBill API returns a JSON if the URL extention is .json or an XML if the URL extention is .xml.
The HTTP methods (verbs) used in the request are described in the documentation:
\n\nGET requests to retrieve resource representation/informationPOST to create new resourcesPUT to update existing resourceDELETE to delete resourcesResponses headers are Content-Type application/json; charset=UTF-8 if the request was JSON or Content-Type application/xml; charset=UTF-8 if the request was XML.
Response HTTP code is 200 if method was executed with success or
4XX if we deal with a validation error.5XX if we deal with an internal error.