Invalid rule error on Create Rule Component using Launch API | Community
Skip to main content
S
swirl1
June 8, 2022
Solved

Invalid rule error on Create Rule Component using Launch API

  • June 8, 2022
  • 1 reply
  • 1049 views

I'm getting the below error while I use the API https://developer.adobelaunch.com/api/reference/1.0/rule_components/create/ even though I send the correct structure for the payload using python as mentioned in the link. 

"errors": [{
"code": "invalid-rule",
"title": "Invalid rule",
"detail": "can\'t be blank",
"source": {
"pointer": "/data/attributes/rule"}
Please note that the data/attributes/rule is not part of the attributes or the request response.

Can you please help in this regard to eliminate this error?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by swirl1

Hi @parvesh_parmar Yes, I had a look at it. The structure of 'rules' is under 'relationships' and not 'attributes'. But the source pointer says 'data/attributes/rule' , hence, I've a question if the schema is not updated to include 'rule' in 'attributes' ? Or is there anything else that's missed out?

Thanks!

1 reply

Parvesh_Parmar
Community Advisor
Parvesh_ParmarCommunity Advisor
Community Advisor
June 9, 2022

Hello @swirl1, 

 

Did you check the following documentation? There they explained the meaning of each parameter of response. 

Error Handling | Adobe Experience Platform

 

 

In your request, you send the data in following format: 

 

Therefore source pointing to that one. 

 

 

Thanks.

Parvesh.

 

 

 

 

Parvesh Parmar – Adobe Community Advisor https://www.linkedin.com/in/parvesh-parmar/
S
swirl1AuthorAccepted solution
June 10, 2022

Hi @parvesh_parmar Yes, I had a look at it. The structure of 'rules' is under 'relationships' and not 'attributes'. But the source pointer says 'data/attributes/rule' , hence, I've a question if the schema is not updated to include 'rule' in 'attributes' ? Or is there anything else that's missed out?

Thanks!

Terms & ConditionsAccessibility statement

Loading footer...