SEQ-2b return 404 Not Found

I looked into your issue. The issue was with your account setup. I have changed the permissions for your account so that the one user now can create, etc...cases and not just view them.

Brian

All comments

For creation of any case, GroupID is required.I believe you mentioned particular GroupId for creation of case like below sample.

{

"groupId":"e340d04d-0f58-40d5-a5c6-a0cf0536410b",

"entityType":"INDIVIDUAL",

"providerTypes":[
"WATCHLIST"
],

"name":"SUKUMAR CHANDRA SAHA",

"customFields":[

{

"typeId": "0a3687d0-5c1b-1fcb-9708-1bde000000a4",

"value":"Shilpi"

}

"secondaryFields":[

{
"typeId":"SFCT_1",
"value":"MALE"
},

{
"typeId":"SFCT_2",
"dateTimeValue": "2016-10-12"
},

{
"typeId":"SFCT_3",
"value":"IND"
},

{
"typeId":"SFCT_4",
"value":"IND"
},

{
"typeId":"SFCT_5",
"value":"IND"
}
]

}

In this example I am using "groupId":"e340d04d-0f58-40d5-a5c6-a0cf0536410b"(SampleClientAPI-Group1-1)for creation of case and using particular case template which are using for this Group.

If you can maintain the same process you should get the correct result.

Let me know if still getting any error.

Thanks,

Shilpi

With the assumption that I can invoke the SEQ-1b API, I believe I'm using group ID correct and still...404.

Can you please share your body alongwith API key,API SECRET and error screenshot for creation of simple case.SEQ-2B body.

Thanks,

Shilpi

Here's the body and Error response screenshots. I don't think is a good idea to share API Key / Secret over here in a forum. Again, if I manage to invoke SEQ-1a and SEQ-1b, I'll believe I have the key and secret setup correctly.

Providing your screenshot groupId is missing .Can you please put the correct groupId as mentioned above in example for creation of case.

Thanks,

Shilpi

As I mentioned, groupId is setup correctly. Otherwise I won't be able to run SEQ-1b. There's no need to manually configure the group ID in body key value as it's all from Postman environment variable.

Anyway, here you go (see below screenshot) and as expecte, 404 still.

Thanks for all of your providing information. Without adding groupId in body you can get 404 error. Can you please share below screenshot with me.

1)SEQ-1A response .

2)SEQ-1B response.

3)Environment variable screenshot want to replicate the same issue in my environment.

Thanks,

Shilpi

To answer your statement on "Without adding groupId in body you can get 404 error", I do have groupId in body using postman environment variable. And I'm using the postman collections file from Thomson Reuters as is without editing it further except adding in Key, Secret and GroupID environment variable.

3 screenshots as per request:

env variable

Thanks for all your information. Providing your groupID I am not able to replicate the groupName in WCI Application(https://app.accelus.com).Not sure what particular credentials you created for this group otherwise we all can able to see this group in WC1 application itself. I will investigate further and let you know whats the issue.

Thanks,

Shilpi

Let me know if you need more screenshot on how it looks like on my app.accelus.com dashboard. I can grab those screenshot and email to your Thomson Reuter email address instead of posting it here in public.

brian.bourgault

The group BaskaranGroup you're using does not have permissions for the SampleUser WC1API.

Please use the SampleClientAPI-Group1 (418f28a7-b9c9-4ae4-8530-819c61b1ca6c) for your trial test.

Brian

Hi @brian.bourgault,

The groupId I'm using is not "BaskaranGroup". It's the group created in app.accelus.com dsahboard. I have no idea what is "BaskaranGroup" and that the "SampleUser" you mention here.

I have change my groupID to the "SampleClientAPI-Group1", now my SEQ-1b is returning 404 (which used to run successfully with my own groupID).

Most importantly, the SEQ-2b still returning 404 not found and it doesn't help. See my screenshot

brian.bourgault