• List Collections (REST)

    GET /api/v1/collections This lists the collections depending on their Show in Front-office list setting. Response is an array of Collections having each the following properties: Collection properties Name Type Description id integer Collection… more »
  • List Posts (REST)

    GET|POST /api/v1/collections//posts? This is the API equivalent of disp = posts. See: URL Parameters. Note: It doesn’t support param types, because it keeps only content post types, and excludes pages, intros, sidebar… more »
  • List Items (REST)

    GET|POST /api/v1/collections//items? See: URL Parameters. more »
  • Retrieve a Post (REST)

    GET /api/v1/collections//posts/ This is the API equivalent of disp = single. Post properties in the Response Name Type Description id integer Post ID datestart datetime Date of start publishing urltitle string Slug type string… more »
  • Retrieve any item (REST)

    GET /api/v1/collections//items/ This is the equivalent of API end-point "Retrieve a Post" to get an item with any type. more »
  • Search (REST)

    GET /api/v1/collections//search/ This is the API equivalent of disp = search. Possible request params Name Type Description Default page integer Page number 1 per_page integer Count pages per page 10 kind string… more »
  • List Users (REST)

    GET /api/v1/users This lists the users as API equivalent of disp = users. Response is an array of the following properties: Name Type Description found integer Number of found users page integer Current page page_size integer Number users per… more »
  • Retrieve a User (REST)

    GET /api/v1/users/ This is the API equivalent of disp = user. more »
  • Create a User (REST)

    POST /api/v1/users This is API end-point to create a user like admins/moderators can do this from back-office Creating a New User more »
  • Update a User (REST)

    POST /api/v1/users/ This is API end-point to update a user like admins/moderators can do this from back-office Editing an User Account. more »
  • Delete a User (REST)

    DELETE /api/v1/users/ This is API end-point to delete a user like admins/moderators can do this from back-office Users. more »
  • Basic HTTP Authentication (REST)

    When you make a REST API call from one webserver to another, you may add HTTP username (or email address) and passwords to your RESTful HTTP requests. b2evolution will check the provided username (or email address) and password to allow privileges on… more »
  • Cookie Authentication (REST)

    If you are already logged in to b2evolution in a web browser, you will have a session cookie and you can use this cookie to obtain privileges when calling the REST API. This is particularly useful when you use the REST API in a browser, for example in a… more »

Comments on this chapter


Form is loading...