< Back to Tips for developers

Product Evolution: Triggers and Action V0 API retirement last announcement

The Version V0 of the API Triggers and Action has been been marked as deprecated since 30/06/2019 and replaced by a new version (version V1).
This API Triggers and Action version V0 will be removed on 31/07/2022.

Cet article est également disponible en Français

Share

What you need to know about the changes

The difference between Version 0 and Version 1 of the API Triggers and Action is focused on the Trigger section. This section in Version 1 is now clearer and allows you to express routing rules with a wider scope. To know more and understand better, we strongly advise reading the user manual section 13.2 Triggers

Note of attention

All the rules that you may have created using version 0 of the API Triggers and action are still available and will continue being available after 31/07/2022.
The only difference is that you will have to call them using version V1 endpoints when necessary.

Tips

Understanding the new format of the Trigger section


All existing rules are available using version V1 of the API triggers and actions.
Therefore it could be useful calling these already existing rules with GET endpoints from version V0 and version V1 : this way it is easy to identify and understand how the new version V1 trigger section is formatted, in comparison with version V0.


Another possibility is to use the web portal to create simple rules with the tools available, and then inspect the way the json body is created

More details on each of the endpoints below:

Endpoint :
DELETE /api/v0/event2action/actionPolicies/{policyId}

New endpoint :

DELETE /api/v1/event2action/actionPolicies/{policyId}

A simple path change, otherwise the call is identical to the previous version

Endpoint :
GET /api/v0/event2action/actionPolicies/{policyId}

New endpoint :

GET /api/v1/event2action/actionPolicies/{policyId}

For the call, only the path changes
The response is formatted in version V1, but any rule previously created in version V0 is available, albeit in version V1

Endpoint :
GET /api/v0/event2action/actionPolicies/

New endpoint :

GET /api/v1/event2action/actionPolicies/

For the call, only the path changes
The response is formatted in version V1, but all the rules previously created in version V0 are available, albeit in version V1

Endpoint :
POST /api/v0/event2action/actionPolicies/

New endpoint :

 POST /api/v1/event2action/actionPolicies/

The call requires to use version V1 semantics in the trigger section, which is detailed and explained in the user manual section 13.2 Triggers. Another useful source of information is the swagger that gives you an example.

Endpoint :
PUT /api/v0/event2action/actionPolicies/
{policyId}

New endpoint :

PUT /api/v1/event2action/actionPolicies/{policyId}

The call requires to use version V1 semantics in the trigger section, which is detailed and explained in the user manual section 13.2 Triggers. Another useful source of information is the swagger that gives you an example.

 

Reminder below on main access points to the documentation

Swagger: https://liveobjects.orange-business.com/#/cms/documentation-swagger/

Developer guide: https://liveobjects.orange-business.com/doc/html/lo_manual_v2.html

Was this article helpful?

Yes No

Thank you for your input, feel free to leave a comment below to explain your choice.

Your email address will not be published. Required fields are marked *

*

Try Live Objects for free

Get a free account limited up to 10 devices and do not hesitate to contact us to tell us about your project.

Create a LoRa® discover accountCreate an other offer discover account

Sign up to get our newsletter

Subscribe to Orange Datavenue IoT B2B newsletter for global news on everything IoT at Orange Business Services.

Subscribe