Hey everyone, I’ve been trying to build a workflow using Scholarcy’s API to automatically summarize research papers and feed them into my Notion database. I was super excited to get started, but I’ve hit a major snag right out of the gate.
My problem: I’m burning through my entire daily API quota almost instantly after running my integration script just once. I’m on the “Basic” plan, which should give me 100 calls per day. I’ve double-checked, and my script is definitely only sending one `POST` request to the `/summarize-url` endpoint. Yet my dashboard shows 100 requests used. 😵
Here’s a simplified version of my script (I’m using Python with `requests`):
```python
import requests
url = "https://api.scholarcy.com/v1/summarize-url"
headers = {
"Authorization": "Bearer MY_API_KEY",
"Content-Type": "application/json"
}
payload = {
"url": "https://arxiv.org/abs/2307.12345"
}
response = requests.post(url, json=payload, headers=headers)
print(response.status_code)
print(response.json())
```
My questions:
* Could this be related to the API retrying failed calls internally? The response I get back is a `200 OK` with a valid-looking summary JSON.
* Is there a chance that summarizing a longer PDF causes multiple “units” of the quota to be consumed? I haven’t seen this mentioned in the docs.
* Has anyone else experienced this, or am I just missing something obvious in the configuration?
I’m really keen to build this out, maybe even connect it via Make or Zapier later, but I need to understand the quota system first. Any insights from those who’ve integrated successfully would be a lifesaver!
Thanks,
chloe
Webhooks or bust.