2023-11-01 11:57 AM - edited 2023-11-01 12:05 PM
Hello,
I am trying to create/ update a record in Archer Applications table from Postman Application. I am able to obtain the Session ID and get the records from Applications table using the "Obtain Session ID" and "Get Level Metadata". When I tried the create/ update the same using Content Save, it is giving me 401 error.
Please find the details:
Method: POST
Endpoint: <archerURL>/contentapi/Applications
Headers:
Content-Type: application/json
Cookie: ArcherSessionCookie={{sessionToken}}
Accept: application/json,text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
I've tried "__ArcherSessionCookie__", "Archer session-id" Let me know if I have to change anything.
2023-11-01 03:50 PM
I was able to get an update working in my local instance using Fiddler, but I did see a few things that caused trouble.
In none of these cases did I get a response that told me what was actually happening, as you would get in the Platform API. I would recommend the following approach:
If you can get that to succeed, you can increase the complexity until you find the point of failure. If you find something specific causing an issue, you can open a support case to get that addressed.
2023-11-01 08:31 PM
Bodie,
I am using POST method for the update.
Application ID is Unique. The body I am using is:
2023-11-01 10:33 PM
Your Authorization header should look like this
Authorization: Archer session-id=DF4B70880C7DA1CB32927C93658A7978
You'll have to call the /contentapi resource to get the available endpoints.
What response are you getting?
2023-11-01 10:54 PM
2023-11-01 11:03 PM
The Authorization header I sent included a session token from my environment. You'll need to replace the DF4B... value with your own session.
2023-11-01 11:10 PM - edited 2023-11-01 11:10 PM
Yes, I've done that. Replaced the session token with yours while posting the reply.
2023-11-01 11:32 PM
The session token I posted is only valid in my local environment. You will get an HTTP 401 unless you replace it with a session from the instance you are testing against.
2023-11-02 02:10 PM
Sorry, I meant that I've replaced the session token of yours with the SessionToken generated. I have replaced that in this post with your SessionToken.
2023-11-02 02:51 PM
I'd recommend a support ticket. They may be able to tell you why you're getting an HTTP 400.