Authentication

Learn how BookHub Publisher API uses JWT authentication, including header format and token requirements.

Authenticate with the BookHub Publisher API using JWT bearer tokens.

JWT bearer token

All API requests require authentication using a JWT bearer token.

Obtaining a token

Tokens are issued manually by BookHub support. To request one, email api–[e-mail] with your publisher name, account ID, and contact email.

Using the token

Replace YOUR_JWT_TOKEN with the 24–hour JWT provided by api–[e-mail].

Authorization: Bearer YOUR_JWT_TOKEN

curl -X GET https://api.bookhub.com/api/v2/books \
  -H "Authorization: Bearer YOUR_JWT_TOKEN"

Token expiration and renewal

Tokens expire 24 hours after they are issued. To renew, email api–[e-mail] with the same details you used to request the original token (publisher name, account ID, and contact email).

Authentication errors

A request with a missing, malformed, or expired token returns 401 Unauthorized. Authentication errors return only the status and message fields — they do not include the errors array used for field-level validation failures.

{
  "status": "error",
  "message": "Unauthorized: the authentication token is missing, malformed, or expired."
}

Token security

Store tokens securely and never expose them in client–side code, version control, or logs. Rotate tokens immediately if compromised by contacting api–[e-mail].

Next steps

Explore related topics:

How-to guides

• Monitor rate limits — Track your API usage to avoid exceeding rate limits.
• Add the Idempotency-Key header — Add the Idempotency-Key header to prevent duplicates when creating books.

Reference

• API endpoints — Provides additional information about the BookHub Publisher API v2 endpoints, including business rules.
• Code examples — Copy code samples for book creation, sorting by creation date, handling removed title sorting, and tracking performance with hitCount.
• Release notes — Explore all changes in BookHub Publisher API v2.

---