Dummy data?

[Bruno Picinini]

Hi,

we're trying to create a simple script just to get ad costs from each campaign and paste into a .txt file. Trouble is we are finding some issues:

– Does the API only allow 2 calls per hour? That's what we found;
– It seems everytime we send a request we get some dummy data back. Check it out:


Do we need to do anything to change my API from "Test" to "Running" or whatever to make this work?

Thanks
-Bruno

[Bruno Picinini]

Additionally we would like to extend the number of calls per hour we can make to the API.

Thanks

[lr...@outbrain.com]

Bruno, 

Can you send the Amplify Request ID plus the call you are sending to the system?  You need to make sure you are using a valid token when making the calls.  

In the live API you can make 10 calls per minute before you hit the rate limits.

Laine

[lcol...@perk.com]

It's possible that the limit being hit is the 2 /login request limit per hour? (if you're performing a login to obtain a token with each API call / process execution)

Once you obtain a token via the /login edge, I believe you should retain / reuse that token for subsequent requests to avoid hitting the login rate limit (which in my opinion could be increased). There are limits / lifespan associated with the token as well so check the API docs for your specific requirements.

I'm sure Laine will be able to provide more details, having your Amplify Request ID.

Happy Coding.

[Bruno Picinini]

Hi,

thanks for the replies.

Humm. I'll ask my guy to check here to see if that's the issue. He's the one doing the coding.

By Amplify Request ID, you mean my API credentials or is it something else?

BTW, it seems now he's able to get the proper data. Dunno what he fixed/changed. So now there's only this 2/day limit, but it might be the login thing.

Thanks

[Bruno Picinini]

Is it by any chance these 2 numbers at the URL when I visit my account?

One account has id 001cc17a7270164200879e3150c94aeeb7 (name Digital Lifestyle)

The other one has id 009d1cd25ec2b75b0422e3a023c5d09b54 (Empreendedor Digital)

[lr...@outbrain.com]

Bruno, 

Sounds like you've been able to get access to the data so I don't think we need to investigate further using your request ID, but note that you've included the marketer id below the request ID is generated for individual calls to the API.

In regards to the rate limit of 2/hour for logins, you actually only need to login once every 30 days and there is no reason to invoke a login request for each user more than once a day since the token generated is active for 30 days. It seems that you are issuing a login request each time you need to call the API,  but you should save the token and use it for a long period of time.

Hope that helps!

Laine

[Bruno Picinini]

Ok, so that's my marketer ID?

My request ID is my API id?

I got confused.

And isn't it dagenrous to simply post my API key here?

[Amir Matar]

Hi Bruno,

Yes, what you saw in the URL above was your marketer ID.

The amplify request id is a unique identifier assigned to each API request and it allows us to find a given call to the API in our systems.

The API id/key is called token and indeed it shouldn't be posted in this forum.

Let me know if you have more questions.

Amir

--
You received this message because you are subscribed to the Google Groups "Outbrain-AmplifyApi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to outbrain-amplifyapi+unsub...@googlegroups.com.
To post to this group, send email to outbrain-amplifyapi@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/outbrain-amplifyapi/bf6ec55b-3368-4cd9-9146-a9cbe9c3387d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion, and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.

This email and any attachments hereto may be confidential or privileged.  If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person. Thanks.