Governance Endpoints
This document covers the governance endpoints: the policy documents that bind your account, your acceptances of them, the compliance evaluations and notices recorded against your account, and the appeals you may file. Enforcement against sellers is governed by the Seller Enforcement Policy and appeals by the Appeals Policy; the normative text of each policy, including the Selling Terms of Service, controls over any summary here. This document states the endpoint mechanics.
Access through the developer API is issued by the Company and is limited by seller type: manufacturer and supplier accounts receive API access for importing data, under the Developer Agreement and the API Access Tiers. Nothing in this document grants broader access.
Endpoints
| Method | Path | Purpose |
|---|---|---|
| GET | /governance/policies | List the policies in force, with their current versions |
| GET | /governance/policies/{policy_id} | Read one policy's current text and version |
| GET | /governance/acceptances | List your account's policy acceptances |
| POST | /governance/acceptances | Record acceptance of a policy version |
| GET | /governance/evaluations | List compliance evaluations recorded against your account |
| GET | /governance/violations | List violation notices issued to your account |
| GET | /governance/violations/{id} | Read one violation notice in full |
| POST | /governance/appeals | File an appeal against a violation |
| GET | /governance/appeals | List your appeals and their outcomes |
| GET | /governance/audit | List the recorded history of actions on your account |
All paths are relative to the base URL https://www.aapawz.com/api. Collections paginate as specified in Pagination and Filtering (Pagination & Filtering). Writes accept an Idempotency-Key header (Idempotency Keys).
Policies and versions
A policy is identified by a stable policy_id and carries a version. The version in force is the current version; when the Company issues a new version, the new version is announced with its effective date, and the prior version remains readable for reference.
{
"policy_id": "selling-terms",
"title": "Selling Terms of Service",
"version": "4.2",
"effective_from": "2026-09-01",
"acceptance_required": true,
"reference": "[Selling Terms of Service](/docs/legal/sellers/selling-terms-of-service)"
}
Always cite a policy as policy_id plus version: in appeals, in correspondence, and in your own records. "The policy" without a version does not identify the text that governed a decision.
Acceptances
An acceptance records that your account accepted a specific version of a policy. Accept a new binding version promptly: an account that has not accepted the current version of a binding policy may be restricted from listing or selling until it does.
{
"policy_id": "selling-terms",
"policy_version": "4.2"
}
A successful acceptance returns 201
{
"id": "acc_19fe55",
"policy_id": "selling-terms",
"policy_version": "4.2",
"accepted_at": "2026-10-10T16:44:03Z"
}
Acceptance is recorded once per version; accepting the same version again returns the original acceptance record unchanged.
Evaluations and violations
An evaluation is a recorded check of your account, a listing, or an order against a policy, with a result of pass, flag, or fail and details stating what was checked. A violation notice is the formal record that a policy was breached
{
"id": "vio_82kc14",
"policy_id": "seller-enforcement",
"policy_reference": "[Seller Enforcement Policy](/docs/legal/sellers/seller-enforcement-policy)",
"type": "policy",
"severity": "high",
"status": "open",
"description": "Listing offered a prescription product without the required authorization.",
"subject": { "type": "listing", "id": "prod_8f3ka9" },
"created_at": "2026-10-12T10:05:41Z"
}
severity is one of low, medium, high, critical. status is one of open, under_review, resolved, closed. A violation notice states the policy and version breached, the subject, and the action required of you; read it in full before responding. Related holds on stock are described in Inventory Endpoints.
Appeals
One appeal may be filed per violation. File with the evidence the Appeals Policy requires; for appeals turning on purchase or supply records, the evidence standard is the Invoice Evidence for Appeals.
{
"violation_id": "vio_82kc14",
"statement": "The product is an over-the-counter supplement; the listing has been corrected and the authorization letter is attached as evidence.",
"evidence_urls": [
"https://www.aapawz.com/appeals/vio_82kc14/authorization-letter.pdf"
]
}
An appeal carries status of pending, approved, or denied, and when decided, the decision, the deciding date, and the reasons. An approved appeal resolves the violation it answers. A denied appeal ends the appeal for that violation; any further review proceeds as a dispute under the Appeals Policy, not as a second appeal.
Audit history
GET /governance/audit returns the recorded history of governance actions on your account: notices issued, statuses changed, appeals decided: each with the action, the subject, the time, and the before-and-after state. The history is append-only: entries are never edited or deleted, and a correction appears as a new entry. If an action affecting your account is not in this history, contact support@aapawz.com.
Errors
| Status | Code | Cause |
|---|---|---|
| 404 | not_found | No policy, violation, or appeal with that identifier exists in your account |
| 409 | appeal_exists | An appeal has already been filed for this violation |
| 409 | already_accepted | Returned with the original record when the version was already accepted |
| 422 | validation_failed | The appeal statement or evidence is missing or incomplete |
Error bodies follow Error Codes.