Aduvo Developer Documentation
Read Aduvo's public website content and discover resources for agents. The public website API provides marketing articles. It does not grant access to customer accounts, borrower records, or campaign operations.
OpenAPI and discovery
- Aduvo OpenAPI specification — a machine-readable description of the supported public read endpoints.
- Aduvo llms.txt site guide — a concise guide to product and developer resources.
- WordPress REST API index — route and method discovery for this website.
Read public marketing articles
Use GET /wp-json/wp/v2/posts to list published articles and GET /wp-json/wp/v2/posts/{id} to retrieve one. Responses are JSON. The title.rendered, content.rendered, and excerpt.rendered fields contain HTML; treat it as untrusted content when displaying it in your application.
Try reading five articles. Use page and per_page to paginate (1–100 articles per page, default 10). The X-WP-Total and X-WP-TotalPages response headers give totals. Use search to search article text or slug to look up an article by its slug.
Authentication and product integrations
The documented public GET endpoints require no API key. Private content and administrative operations retain WordPress's existing authentication and permission checks. Customer application login credentials are separate from WordPress credentials.
This specification covers public website reads only. For customer-product API, SDK, or MCP access and authentication requirements, contact Aduvo. These resources do not define or promise access to those integrations.
Read the homepage as Markdown
Send Accept: text/markdown to GET /. The response contains Markdown with Content-Type: text/markdown; charset=UTF-8 and Vary: Accept. Send Accept: text/html for the usual homepage. Quality weights, wildcards, and q=0 exclusions are respected; HTML wins otherwise equal preferences. If neither format is acceptable, the homepage returns HTTP 406.
Markdown negotiation is available on the homepage and missing website pages. Other product pages and this guide use HTML. HEAD returns headers without a body. REST endpoints always use their existing JSON format.
Errors and recovery
Missing website pages retain HTTP 404. Request Markdown for a readable error and recovery links, or JSON with Accept: application/json. Unknown paths under /api/ return JSON errors; discover the actual API at /wp-json/.
WordPress REST errors retain their code, message, data, and HTTP status. Added hint and documentation_url fields explain the next step. For example, a missing route returns:
{
"code": "rest_no_route",
"message": "No route was found matching the URL and request method.",
"data": {
"status": 404
},
"hint": "Check the resource ID and request method. Discover available routes at /wp-json/ or /openapi.json.",
"documentation_url": "https://aduvo.com/developers/"
}For HTTP 400, correct the parameters identified in data.params. For 401 or 403, check authorization rather than retrying anonymously. For 404, check the route, ID, and method. For 429, wait and honor Retry-After if present. For a server error, retry later and contact Aduvo if it persists.