API key auto expire?

bugs
1

Anyone have this issue?

Details:
Manager.io Cloud version
Use access token to create Endpoint and Secret
Every when I create a new key everything will work but after few hours it simply just don’t work anymore. generate a new key will work again.

the Endpoint is a ipv6 address but it shouldn’t be the issue, every time when i create the api key i can see the end point stay the same.

the login account use for create api key is a administrator account, not the default Administrator but created a new user with admin right.

i tried to use different admin account and having the same result.
any hints? or somewhere have setting to control expiry hours for the key?

2

Hello @stevenluk,

Unfortunately, I cannot reproduce your issue on Cloud version 26.6.17.3647.

It looks like your case needs some digging, I would start by reconfiguring the server connection to ipv4 and seeing if that solves it.

3

On another thought, I just revceived this error:

[DataSource.Error]
Web.Contents failed to get contents from 
   'https://agileas.manager.io/api2/employees'
   (429): Too Many Requests

This is what I have feared for a long while. I have been proposing for quite a while to be able to query entire tab screens/Advanced Queries outputs with a single request instead of having to query an index and later query every individual record separately to get custom fields.

@lubos, please let us know about these limits, whether they are here to stay, and if there is any way around them.

@stevenluk, from the above I see that there is text explaining why my request didn’t go through. What does your error message says?

4

Additionally, I tried to create a new token and it gave me this endpoint:

image
image1012×302 9.36 KB

Which in turn resulted in this error:

The endpoint
'https://2a05-d014-591-9700-85bd-6a85-46fd-7f27.ip.manager.cloud/api2' 
cannot be resolved

The only workaround I can think think of is to get daily backups and use those on Desktop edition for connecting with Api2.

I will test and report back.

5

@stevenluk,

Desktop version works just fine for me. Maybe you should give it a try.

6

New finding:
End point also change, today it changed.

any better method or work around?
desktop version won’t have problem because it is local machine.

But I need to use cloud version and used it for a lot of years.
any possible way to use ipv4?
when i access manager i always use https://xxxxxx.manager.io

possible to add something such as /(business_id) to replace the end point?
possible to use login and password pair?

the api key still having the same issue, i can’t keep regenerate api for all business before run the import.

now everything return 201 to me but just a few moments later it won’t work and i need to create the key again.

7

my message just simply unauthorized when it have error. (time limited key?)
i know all api will have too much request issue so i put in sleep(0.5) between each request.
I just put in a simple post request only
requests.post(url, headers=headers, json=payload, verify=False, timeout=30)

not the payload’s issue, the payload is not big only 40 lines total less than 300 characters.

8

I’m not exactly sure what is the issue here, but I will still place this into bugs for now untill we get the confusion cleared

9

Any news abuot this issue?? I’m trying the API and works locally from my computer, but when I deploy to the server it gets error 429 every time. Even early in the morning.