Free tier · no payment method required

Author API

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

Live demo

Try the Author API in your browser

Run the allowlisted author preset against the real Glade backend. Parameters are predefined and validated before an upstream request is made.

Try the Author API

Run the predefined request before writing a single line

GET/api/amazon/author
asin0134685997domainUSpage1
example response · ready
{
  "data": {
    "amazonAuthor": {
      "name": "Example author",
      "biography": "Author profile and public bibliography.",
      "bookResults": {
        "results": [
          {
            "asin": "0134685997",
            "title": "Example book"
          }
        ],
        "pageInfo": {
          "currentPage": 1,
          "hasNextPage": false
        }
      }
    }
  }
}
Endpoint

What does the Author API return?

The Author operation is available through every Glade interface and resolves through the same validation and normalized output contract.

Developer First

How do you call the Author API in seconds?

Use /api/amazon/author without maintaining marketplace-specific acquisition, parsers, retry rules, or response adapters.

One schema, every operation

Use this API alongside 16 other Glade operations without changing authentication or the response envelope.

Metadata, not guesswork

Every response includes request, cache, freshness, rate-limit, and usage metadata for production decisions.

See the contract before coding

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()
[ .JSON ]
{
  "data": {
    "amazonAuthor": {
      "name": "Example author",
      "biography": "Author profile and public bibliography.",
      "bookResults": {
        "results": [
          {
            "asin": "0134685997",
            "title": "Example book"
          }
        ],
        "pageInfo": {
          "currentPage": 1,
          "hasNextPage": false
        }
      }
    }
  }
}
One API, 13 marketplaces

How does Glade normalize author across Amazon marketplaces?

Amazon storefronts vary by host, currency, locale, delivery context, and available fields. Glade keeps those differences behind one versioned author contract.

One schema, every marketplace

One documented contract.

13 Amazon storefronts use one marketplace code, validation layer, and output contract.

data.amazonAuthor marketplace: US success: true
Currency and locale included

Context stays attached.

Marketplace, currency, delivery context, request ID, cache state, and fetch time travel with the normalized response.

cache: HIT fetched_at: 2026-08-16T12:00:00Z usage_units: 1
REST, GraphQL, and MCP

One key, every interface.

Keep one server-side API key while application code and agents use the interface that fits their workflow.

REST: /api/amazon/author GraphQL: amazonAuthor MCP: get_amazon_author
Operation-level freshness

Caching fits the data.

This endpoint uses a 1 day cache policy so volatility and request cost stay explicit.

cache_ttl: 86400 rate_limit: documented request_id: glade_...
Glade Amazon API17 endpoints supported
View docs
GET/api/amazon/author?asin=0134685997&domain=US&page=1
asin0134685997domainUSpage1
curl 'https://gladeapi.com/api/amazon/author?asin=0134685997&domain=US&page=1' \
  -H 'API-KEY: glade_live_YOUR_API_KEY'
example response · ready
{
  "data": {
    "amazonAuthor": {
      "name": "Example author",
      "biography": "Author profile and public bibliography.",
      "bookResults": {
        "results": [
          {
            "asin": "0134685997",
            "title": "Example book"
          }
        ],
        "pageInfo": {
          "currentPage": 1,
          "hasNextPage": false
        }
      }
    }
  }
}
Compare

How does Glade's Author API compare to a self-managed integration?

Glade packages author acquisition, validation, normalization, caching, errors, and request metadata behind one server-side key.

FeatureGlade APISelf managed
AuthenticationOne API-KEY headerSource-specific credentials or sessions
Setup requiredCreate a key and call the endpointBuild acquisition, parsing, retries, and adapters
Marketplace support13 stores through one contractSeparate host and locale handling
Response schemadata.amazonAuthorSource-specific page structures
Freshness1 day policy with metadataYour team owns caching and observation time
InterfacesREST, GraphQL, MCP, and SkillYour team maintains each adapter

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.

Can I use author data in production?

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

Have a question? We got answers

Answers about this Glade API, its parameters, interfaces, freshness, and production use.

How do I call the Author API?
Create a Glade key, send a GET request to /api/amazon/author with one of the documented identifier or query presets, and read data.amazonAuthor from the response envelope.
What does the Author API return?
Get an author profile and books using a book ASIN. Optional fields remain optional, and every response includes request and freshness metadata needed for production handling.
Which marketplaces support author?
Use the same operation across 13 supported Amazon marketplaces by passing the documented domain code.
How fresh is author data?
This operation uses a 1 day cache policy. Read the cache-state and data-fetched-at headers instead of inferring freshness from when your application received the response.
Can I use the Author API with an AI agent?
Yes. The get_amazon_author MCP tool and generated documentation expose the same allowlisted operation and validation rules.
Can I use the Author API in production?
Yes. Keep keys server-side, validate optional fields, store request IDs, use bounded retries for temporary failures, and review source rules and third-party rights for your use case.
Contract statistics

API contract at a glance

Current Author details generated from Glade's versioned operation catalog.

13

marketplaces

1 day

cache policy

3+

interfaces

Ready to call the Author API?

Create a key, keep it server-side, and run the predefined request in minutes.

Get an API key