Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.archeraffiliates.com/llms.txt

Use this file to discover all available pages before exploring further.

Every endpoint outside of POST /token itself requires a bearer token in the Authorization header.

​
Get a token

POST /token accepts your Archer username and password as application/x-www-form-urlencoded and returns an access token. 
curl -X POST https://api.archeraffiliates.com/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "username=YOUR_USERNAME&password=YOUR_PASSWORD"

​
Authorize subsequent requests

Send the token as a Bearer header on every call: 
curl https://api.archeraffiliates.com/getproducts \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
Tokens last long enough for normal use. If a call returns 401, fetch a fresh token and retry.

​
Publisher vs. seller credentials

Use the same POST /token flow for both account types. What you can call is determined by the account, not by a separate auth flow:
  • A publisher account can hit the Publisher API endpoints.
  • A seller account can hit the Seller API endpoints (/sellers/...).
The Seller API is mounted under /sellers, so for example /sellers/reports is the brand-owner equivalent of the publisher’s /reports.