eno.vn Partner API
Manage your eno.vn storefront programmatically — from your own systems or an AI agent. A REST API with bearer-key auth, supporting read and write.
Base URL
https://eno.vn/api/v1Everything below is served from https://eno.vn.
Specs & discovery
Machine-readable descriptions of this API. All 9 are public, need no credentials, and are served from this same origin.
- /api/v1/status
The only endpoint in the reference below that needs no credential. Edition, API version, links to everything below — and live RateLimit headers, so you can see the throttle before you have a key. Start here.
- /openapi.json
OpenAPI 3.1 description of every endpoint below — point a codegen or an agent at this first.
- /llms.txt
What this site is and when to use it, written for an agent rather than a crawler.
- /sitemap.xml
Every public URL. Open, no credentials.
OAuth, MCP and catalogue metadata, and the spec alias
- /api/v1/openapi.json
The same document at its original path, kept because partner codegen configs already reference it.
- /.well-known/oauth-authorization-server
RFC 8414 metadata: the token endpoint, the supported grant, and the scope list.
- /.well-known/oauth-protected-resource/api/v1
RFC 9728 metadata: which resource the token is for, and which server issues it. An agent that gets a 401 reads this to find its way in.
- /.well-known/mcp.json
MCP Server Card: the hosted Model Context Protocol server at /api/mcp, its transport, its protocol versions, and the Bearer header to connect with. Point an MCP client here.
- /.well-known/api-catalog
RFC 9727 API catalogue: this API and the MCP server, each with its spec, docs and status links, as a Linkset.
Nothing here requires an account. Together with GET /status below, this is what you can call before you have a key:
curl https://eno.vn/openapi.jsonOr from a terminal, with the eno.vn CLI: npx eno-vn status.
Authentication
A key is live from the moment it is issued — to try the API first, use the sandbox. Create a key in your dashboard → Developers section (business accounts). The full secret is shown once — store it safely. Send it as a Bearer token on every request:
Authorization: Bearer eno_live_…- • Scopes:
listings:read,listings:write,analytics:read,media:write(write is opt-in when you mint the key). - • One shop per key: requests only ever see that shop's own data.
- • Revoke anytime: the key stops working at once; an OAuth token already minted from it keeps working until its one-hour lifetime ends.
eno.vn and its sibling site run the same software on separate deployments, and they share one database — so a key issued by either one authenticates at both. Send requests to the host you got your key from anyway: that is the host whose catalogue and storefront the responses describe. Treat a key as a credential for your shop, not for a single hostname, and revoke it in the dashboard if it leaks.
OAuth 2.0 (optional) — short-lived tokens
Prefer not to put the long-lived key on every request? Exchange it for a 1-hour bearer token via the client-credentials grant — client_id is the key's prefix, client_secret is the full key. Optionally pass scope to narrow the token (it can never exceed the key's scopes). The returned token works anywhere the key does, including the MCP server. Tokens last one hour. Credentials may go in the body as below, or in an HTTP Basic header.
A client that would rather discover this than read it: the token endpoint, the one supported grant and the scope list are published at /.well-known/oauth-authorization-server, and the resource those tokens are for at /.well-known/oauth-protected-resource/api/v1.
curl -X POST https://eno.vn/api/v1/oauth/token \
-d grant_type=client_credentials \
-d client_id=eno_live_PREFIX -d client_secret=eno_live_FULLKEY
# → { "access_token": "eyJ…", "token_type": "Bearer", "expires_in": 3600, "scope": "listings:read analytics:read" }
# then: Authorization: Bearer eyJ…Sandbox
Try the API without an account or real data. A test key needs no sign-up, lasts 24 hours and works only under https://eno.vn/api/v1/sandbox: sample listings in the live shapes, create and update calls that run the live checks and store nothing, and an export that runs as an async job. Every response there carries X-Sandbox: true. Step by step: the sandbox page.
curl -X POST https://eno.vn/api/v1/sandbox/keys
# → { "key": "eno_test_…", "type": "test", "expires_at": "…", "base_url": "https://eno.vn/api/v1/sandbox", "sandbox": true }
curl "https://eno.vn/api/v1/sandbox/listings?q=honda" -H "Authorization: Bearer eno_test_…"
curl -i -X POST https://eno.vn/api/v1/sandbox/exports -H "Authorization: Bearer eno_test_…"
# → 202 Accepted, Location: https://eno.vn/api/v1/sandbox/exports/job_…
# poll that URL until "status": "done"; the result is in the same responseManage your shop with AI (MCP)
eno.vn runs a hosted Model Context Protocol server, so an AI agent (Claude, etc.) can manage your storefront directly — list, create, edit, bulk-import, sync a catalogue, read analytics, and manage webhooks. Add it as a remote MCP server with your API key as the Bearer token:
https://eno.vn/api/mcp
Authorization: Bearer eno_live_…Your key stays in the client's connection settings — no tool takes it as an argument, so the server never asks the model for it. Keep it out of chats.Tools are scoped exactly like the REST API: a call whose key lacks the tool's scope is refused. Available tools:
get_shopupdate_shoplist_listingsget_listingcreate_listingupdate_listingset_listing_statusdelete_listingbulk_create_listingssync_catalogueanalytics_summaryanalytics_listingslist_webhooksregister_webhookdelete_webhooklist_conversationsget_conversationcontact_sellersend_messagedecline_offer
Setup for Claude Code and other clients, and what each tool needs: eno.vn MCP server. Also on npm as eno-vn-mcp, in the official MCP Registry as vn.eno/partner-api and vn.eno/search, with agent skills and an AGENTS.md at eno-agent-skills.
Search with an A2A agent
The listing search also answers over Agent2Agent (A2A), JSON-RPC, versions 1.0 and 0.3, with no key. Its Agent Card is at /.well-known/agent-card.json. Send a text part (what to look for, or a listing's URL) or a data part with the search fields. The answer is one message: a short summary and the results as JSON. Read-only: no sign-in, no tasks, no streaming.
POST https://eno.vn/api/a2a
A2A-Version: 1.0
{"jsonrpc":"2.0","id":1,"method":"SendMessage","params":{"message":{"messageId":"1","role":"ROLE_USER","parts":[{"text":"honda vision district 3"}]}}}Conventions
- • Rate limit: 600 requests/min per key. Responses carry
X-RateLimit-Limit/X-RateLimit-Remainingand anX-Request-Id. - • Pagination: list endpoints are keyset-paged — pass
?limit=(≤100) and?cursor=; follownext_cursoruntil it'snull. - • Errors:
{ "error": { "code", "message" } }— e.g.401 unauthorized,403 insufficient_scope,404 not_found,422 invalid_input,429 rate_limited. - • Versioning: the version is in the path (
/api/v1); additions ship without notice, a breaking change ships as a new path. How a deprecation is announced: versioning and deprecation policy. - • Idempotency: on a create, send
Idempotency-Key: <unique-id>— a retry replays the first result instead of creating twice.
Endpoints
/statusService status and discovery. The only endpoint here that needs NO credential — and the one to call first, because its RateLimit headers tell you the throttle before you have a key.
curl -i https://eno.vn/api/v1/status/shopYour storefront profile, trust score, and live listing count.
curl https://eno.vn/api/v1/shop \
-H "Authorization: Bearer eno_live_…"{ "shop": { "id", "name", "bio", "location", "phone",
"avatar_url", "trust_score", "trust_tier",
"response_rate", "member_since", "active_listings" } }/listingsYour listings — ALL statuses (active, sold, hidden, held). Keyset-paginated.
curl "https://eno.vn/api/v1/listings?limit=50" \
-H "Authorization: Bearer eno_live_…"{ "listings": [ { "id", "title", "price", "status",
"verified", "images", "category", … } ],
"next_cursor": "eyJ…" | null }/listings/{id}A single listing of yours, any status. 404 if it isn't yours.
curl https://eno.vn/api/v1/listings/LISTING_ID \
-H "Authorization: Bearer eno_live_…"{ "listing": { "id", "title", "price", "status", … } }/analytics/summaryShop rollup: total views + leads and listing counts by status.
curl https://eno.vn/api/v1/analytics/summary \
-H "Authorization: Bearer eno_live_…"{ "summary": { "total_listings", "total_views",
"total_leads", "active", "sold", "hidden", "held" } }Write — scopes: listings:write / media:write
/listingsCreate a listing. Body: categorySlug, title, price + optional description, images[], district, condition, listingType, brand, model… Send an Idempotency-Key to make retries safe.
curl -X POST https://eno.vn/api/v1/listings \
-H "Authorization: Bearer eno_live_…" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"categorySlug":"electronics","title":"iPhone 14 Pro",
"price":18000000,"images":["https://…/api/….webp"]}'{ "listing": { "id", "verified" } }/listings/{id}Edit a listing (sparse — only the fields you send change).
curl -X PATCH https://eno.vn/api/v1/listings/LISTING_ID \
-H "Authorization: Bearer eno_live_…" -H "Content-Type: application/json" \
-d '{"price":16500000,"condition":"used"}'/listings/{id}/statusSet availability: active | sold | hidden.
curl -X POST https://eno.vn/api/v1/listings/LISTING_ID/status \
-H "Authorization: Bearer eno_live_…" -H "Content-Type: application/json" \
-d '{"status":"sold"}'/listings/{id}Remove a listing.
curl -X DELETE https://eno.vn/api/v1/listings/LISTING_ID \
-H "Authorization: Bearer eno_live_…"/mediaUpload an image (multipart `file`, or a raw JPEG/PNG/WebP body). Returns a first-party URL to use in images[]. Scope: media:write.
curl -X POST https://eno.vn/api/v1/media \
-H "Authorization: Bearer eno_live_…" \
-F file=@photo.jpg{ "url": "https://sb.eno.vn/storage/v1/object/public/listings/….webp" }/shopEdit your storefront profile (name, bio, location, avatarUrl, phone).
curl -X PATCH https://eno.vn/api/v1/shop \
-H "Authorization: Bearer eno_live_…" -H "Content-Type: application/json" \
-d '{"bio":"Authorized reseller in District 1"}'Bulk & catalogue sync — scope: listings:write
/listings/bulkCreate up to 200 listings in one call. Each row is independent (one bad row never aborts the batch); remote image URLs are re-hosted. Send an Idempotency-Key so a retry can't import twice. Returns per-row results.
curl -X POST https://eno.vn/api/v1/listings/bulk \
-H "Authorization: Bearer eno_live_…" \
-H "Idempotency-Key: $(uuidgen)" -H "Content-Type: application/json" \
-d '{"listings":[
{"categorySlug":"electronics","title":"iPhone 14","price":15000000,
"images":["https://your-cdn/iphone.jpg"],"externalId":"SKU-1"},
{"categorySlug":"electronics","title":"AirPods Pro","price":4500000}
]}'{ "created": 2, "failed": 0, "image_budget_reached": false,
"results": [ { "row": 1, "id": "…", "external_id": "SKU-1", "error": null }, … ] }/listings/syncUpsert your catalogue by your OWN id (externalId, unique per shop) — create new SKUs, update existing ones in place. mode: 'partial' (default) only touches the rows you send; 'full' also RETIRES (hides) any active listing whose externalId is NOT in the payload, so your storefront mirrors your system. Naturally idempotent. Up to 200 rows.
curl -X POST https://eno.vn/api/v1/listings/sync \
-H "Authorization: Bearer eno_live_…" -H "Content-Type: application/json" \
-d '{"mode":"full","listings":[
{"externalId":"SKU-1","categorySlug":"electronics","title":"iPhone 14",
"price":14500000,"status":"active","images":["https://your-cdn/iphone.jpg"]},
{"externalId":"SKU-2","categorySlug":"electronics","title":"iPad Air","price":12000000}
]}'{ "mode": "full", "created": 1, "updated": 1, "retired": 3, "failed": 0,
"results": [ { "external_id": "SKU-1", "id": "…", "action": "updated" }, … ] }Per-listing analytics — scope: analytics:read
/analytics/listingsDaily views + leads (per-day deltas) for each of your listings over a date range, plus current totals. Keyset-paginated by listing. ?from=YYYY-MM-DD&to=YYYY-MM-DD (default last 30 days, max 92).
curl "https://eno.vn/api/v1/analytics/listings?from=2026-06-01&to=2026-06-29&limit=50" \
-H "Authorization: Bearer eno_live_…"{ "range": { "from", "to" },
"listings": [ { "id", "external_id", "title", "status",
"views_total", "leads_total",
"daily": [ { "day": "2026-06-28", "views": 12, "leads": 1 }, … ] } ],
"next_cursor": "eyJ…" | null }Webhooks — scope: listings:write (register) / listings:read (list)
/webhooksRegister an HTTPS endpoint to receive SIGNED listing events (listing.created / .updated / .status_changed / .deleted), or pass events:'*' for all. The signing secret is returned ONCE — store it. Up to 10 endpoints per shop. The url must be a public HTTPS address.
curl -X POST https://eno.vn/api/v1/webhooks \
-H "Authorization: Bearer eno_live_…" -H "Content-Type: application/json" \
-d '{"url":"https://your-app/webhooks/eno","events":["listing.created","listing.updated"]}'{ "webhook": { "id", "url", "events": ["listing.created","listing.updated"],
"enabled": true, "created_at", "secret": "whsec_…" } }/webhooksList your registered webhook endpoints (secrets are never returned). Shows delivery health: failure_count, last_error, last_delivery_at. An endpoint auto-disables after repeated failures.
curl https://eno.vn/api/v1/webhooks -H "Authorization: Bearer eno_live_…"/webhooks/{id}Unregister a webhook endpoint.
curl -X DELETE https://eno.vn/api/v1/webhooks/WEBHOOK_ID -H "Authorization: Bearer eno_live_…"Verifying webhooks. Deliveries follow the Standard Webhooks spec, so any off-the-shelf verifier works. Each POST carries webhook-id, webhook-timestamp and webhook-signature (v1,<base64>) — an HMAC-SHA256 of ${id}.${timestamp}.${body} keyed by your whsec_ secret. Reject anything that doesn't verify.
{ "id": "msg_…", "type": "listing.updated",
"created_at": "2026-06-29T…Z",
"data": { "listing_id": "…", "status": "sold" } }Questions or need write access early? support@eno.vn.