Login API is working fine but Account details API give 401 error

[praveenbaranwal]

I am trying to login using below API calls in postman client where i get the response as expected.
Req type: POST
URL: Target URL
Body has following parameter
email: praveenbaranwal
password: praveen123
api_key: sweedelight800
rt: a/account/login

I am able to get the login Success with response code 200.

Next i wanted to validate my login:
Req type: POST
URL: Target URL
Body has following paramater
token: use the value received in step 1
api_key: sweedelight800
rt: a/account/login

I am getting the response code as 200 and Authorized.

The same query was sent using a java class file created (Attached java class file) but i am getting error in the 2nd part where i am trying to validate if i am logged it.

I am not sure if token will be sent as header (if yes how?).

Regards,
Praveen
+91-9739048200

[abantecart]

I wonder if your Java class pass session/cookie in the request. How do you pass token back to the next request?

[abolabo]

you can enable Debug mode in your Abantecart settings with output to log-file.
Also you can add your own logging inside api-controllers to recognise all environment variables

[panthersam]

Hello praveenbaranwal,

I need a help from you.How can i make big search bar like your site.Can you suggest me .

[praveenbaranwal]

Hi Sam,

You can edit the Search field size by
1)goto file: public_html/storefront/view/default/stylesheet/style.css
2) Search for
.top-search input {
   width: 100%;
   border: 4px solid #F5F5F5;
   padding: 6px;
   float: left;
   vertical-align: middle;
}
Now edit the width % based on your choice. You can also choose where to keep the search box (Left or right)

Hope this helps.

Regards,
Praveen

[Rawinder Dhillon]

parveen , did you solved the problem

[Rawinder Dhillon]

dont know it is helpful or not for parveen now but may be helpful for someone else :-)
i solved this one
in 2nd step use
rt: a/account/account instead of rt: a/account/login
and we need to send cookies in headers that mainly include session and customer cookies that we received in step 1.