Change Details

When a `group_1` user hist `structured-contents` API endpoint, he needs to be able to do `10k` API calls (like our currently available on-demand `articles` endpoint), so that he can easily test out the endpoint and see whether it's a fit for his product. **Acceptance criteria** As a `group_1` user I'm able to make `10k` API requests to `structured-contents` endpoint in a lifetime. **ToDo** - [ ] update access policies in the `main` API and infrastructure to allow access - [x] expand the same middleware that's applied to `/v2/articles` endpoint to `structured-contents` endpoint (we should be able to use the same `httputil.Cap` middleware) - [ ] test it thoroughly in `dev` environment (you can reduce the threshold) **Notes** There's no need to do any UI changes or anything like that, as our `structured-contents` endpoint falls under On-demand API current dashboard visualization of requests left should do the job.

When a `group_1` user hist `structured-contents` API endpoint, he needs to be able to do `10k` API calls (like our currently available on-demand `articles` endpoint), so that he can easily test out the endpoint and see whether it's a fit for his product. **Acceptance criteria** As a `group_1` user I'm able to make `10k` API requests to `structured-contents` endpoint in a lifetime. **ToDo** - [x] update access policies in the `main` API and infrastructure to allow access - [x] expand the same middleware that's applied to `/v2/articles` endpoint to `structured-contents` endpoint (we should be able to use the same `httputil.Cap` middleware) - [x] test it thoroughly in `dev` environment (you can reduce the threshold) **Notes** There's no need to do any UI changes or anything like that, as our `structured-contents` endpoint falls under On-demand API current dashboard visualization of requests left should do the job.

When a `group_1` user hist `structured-contents` API endpoint, he needs to be able to do `10k` API calls (like our currently available on-demand `articles` endpoint), so that he can easily test out the endpoint and see whether it's a fit for his product. **Acceptance criteria** As a `group_1` user I'm able to make `10k` API requests to `structured-contents` endpoint in a lifetime. **ToDo** - [ - [x] update access policies in the `main` API and infrastructure to allow access - [x] expand the same middleware that's applied to `/v2/articles` endpoint to `structured-contents` endpoint (we should be able to use the same `httputil.Cap` middleware) - [ - [x] test it thoroughly in `dev` environment (you can reduce the threshold) **Notes** There's no need to do any UI changes or anything like that, as our `structured-contents` endpoint falls under On-demand API current dashboard visualization of requests left should do the job.