Bug Report: API returns inaccurate results due to Access Token constraints

[chriscerk]

I'm formally logging here as a bug since the API not returning accurate data is not expected.

(the support email thread got logged in the below discussion item, but I think this should be treated as a bug - not a new feature)

Related items

• [API] Create endpoint to trigger a resync
• Document limitations for machine users when using Codecov API #329

The current work-a-round for getting accurate data for an access token is quite lengthy:

• manually sign in as the user which the access token was provisioned
• click the re-sync repo's button via the UI

This isn't acceptable for a programatic use of the API.

---

Describe the bug
A clear and concise description of what the bug is.

Calling the codecov API via an access token does not return accurate data.

Environment (please complete the following information):

• System: any use of an access token

To Reproduce
Steps to reproduce the behavior:

1. Have a large number of repositories
2. Create an access token and call the active repos via a script
3. Create new repositories
4. Note that new repositories and other calls relying on those new repositories will fail

Expected behavior
A clear and concise description of what you expected to happen.

We are able to call the codecov API and get accurate data.

Either via

• [API] Create endpoint to trigger a resync
• or using some other authentication method not based on these access tokens which have constraints

[claym-ih]

👍

[chriscerk]

Any updates on this?

(even if it is a "no we won't support this" or this will re-prioritized in MM/yyyy)