Two prices
- Find. Calls that discover things, such as search, similar products and trending, cost 10 API credits per page with results.
- Retrieve. Calls about something you named, such as a product, a shop, a keyword or one page of a shop’s reviews, cost 1 API credit per call, page or item.
GET /v1/me, GET /v1/usage, categories and languages, switching workspace, and the saved folders and lists themselves.
Nothing is charged for:
- errors, of any kind;
- a
202pending answer while Alura fetches something new; - an empty page or an empty result;
- items in a bulk call that come back pending, unfetched or not found;
expand=, which adds related objects to a response at no cost.
Allowances
- The month is the calendar month in UTC, and unused API credits don’t carry over.
- On Basic, Growth and Professional, one UTC day can use at most a quarter of the month. Free can spend all 100 in one day.
- An upgrade applies at once, and what you used this month counts toward the new allowance.
Seeing what you spend
Every authenticated response carries two headers:_meta.credits_charged. GET /v1/usage shows the month so far, by operation and by client, and GET /v1/usage/events lists every charge from the last 90 days. See Usage and limits.
Running out
Before a call runs, Alura holds the most it can cost, then charges what it really cost and gives back the rest. A bulk call needs enough API credits for every ID up front, even though you pay only for the items that come back.
Cost of every operation
Generated from the API’s operation list, so it always matches what the API charges. The same numbers are in each endpoint’sx-alura-credits in the OpenAPI document and in costs from GET /v1/usage.