How is Author API usage measured?
Successful normalized operations consume the units defined by the active plan. Request headers make usage and rate-limit state visible to your backend.
Get an author profile and books using a book ASIN. Call one documented GET endpoint across 13 Amazon marketplaces with the same API key, normalized response envelope, and production metadata.
TL;DR
The Author API returns structured JSON under data.amazonAuthor. It is available through REST, GraphQL, and MCP, with a 1 day cache policy and explicit request, freshness, rate-limit, and usage metadata.
Use this Glade operation through
Run the allowlisted author preset against the real Glade backend. Parameters are predefined and validated before an upstream request is made.
Run the predefined request before writing a single line
{
"data": {
"amazonAuthor": {
"name": "Example author",
"biography": "Author profile and public bibliography.",
"bookResults": {
"results": [
{
"asin": "0134685997",
"title": "Example book"
}
],
"pageInfo": {
"currentPage": 1,
"hasNextPage": false
}
}
}
}
}The Author operation is available through every Glade interface and resolves through the same validation and normalized output contract.
GET /api/amazon/author returns data.amazonAuthor in the standard response envelope.
amazonAuthor exposes the same normalized operation through the typed GraphQL schema.
get_amazon_author exposes the allowlisted operation to compatible AI agents.
Use /api/amazon/author without maintaining marketplace-specific acquisition, parsers, retry rules, or response adapters.
Use this API alongside 16 other Glade operations without changing authentication or the response envelope.
Every response includes request, cache, freshness, rate-limit, and usage metadata for production decisions.
Copy a request in Python, TypeScript, or cURL and inspect the example JSON before moving into production.
import requests
response = requests.get(
'https://gladeapi.com/api/amazon/author',
params={'asin': '0134685997', 'domain': 'US', 'page': '1'},
headers={'API-KEY': 'glade_live_YOUR_API_KEY'}
)
data = response.json(){
"data": {
"amazonAuthor": {
"name": "Example author",
"biography": "Author profile and public bibliography.",
"bookResults": {
"results": [
{
"asin": "0134685997",
"title": "Example book"
}
],
"pageInfo": {
"currentPage": 1,
"hasNextPage": false
}
}
}
}
}Amazon storefronts vary by host, currency, locale, delivery context, and available fields. Glade keeps those differences behind one versioned author contract.
13 Amazon storefronts use one marketplace code, validation layer, and output contract.
Marketplace, currency, delivery context, request ID, cache state, and fetch time travel with the normalized response.
Keep one server-side API key while application code and agents use the interface that fits their workflow.
This endpoint uses a 1 day cache policy so volatility and request cost stay explicit.
curl 'https://gladeapi.com/api/amazon/author?asin=0134685997&domain=US&page=1' \
-H 'API-KEY: glade_live_YOUR_API_KEY'{
"data": {
"amazonAuthor": {
"name": "Example author",
"biography": "Author profile and public bibliography.",
"bookResults": {
"results": [
{
"asin": "0134685997",
"title": "Example book"
}
],
"pageInfo": {
"currentPage": 1,
"hasNextPage": false
}
}
}
}
}Glade packages author acquisition, validation, normalization, caching, errors, and request metadata behind one server-side key.
Successful normalized operations consume the units defined by the active plan. Request headers make usage and rate-limit state visible to your backend.
Use public data, respect source rules and third-party rights, keep keys server-side, and match retention and downstream processing to your approved use case.
FAQ
Answers about this Glade API, its parameters, interfaces, freshness, and production use.
Current Author details generated from Glade's versioned operation catalog.
13
marketplaces
1 day
cache policy
3+
interfaces
Create a key, keep it server-side, and run the predefined request in minutes.
Get an API key