Aramisauto Vehicle Catalog Contracts

name: Aramisauto Vehicle Catalog Contracts
description: 'Aramis Group publishes the machine-readable contracts behind the Aramisauto vehicle catalog
  as ten JSON Schema 2020-12 documents at https://schemas.aramis.group/ — a search request envelope (criteria/facets/order/limit/offset/fields),
  a search response envelope (total/limit/offset/vehicles/facets with 20 pre-bucketed facet aggregations),
  a multi-language vehicle ingest model, the single-language vehicle read model the site itself describes
  as "the format used in the preheated cache for the APIs", a flattened search-index projection, and a
  shared base vocabulary of 29 controlled term sets and unit-bearing value objects. A companion set of
  four schemas describes the collect → map → filter → enrich pipeline a third-party marketplace seller''s
  inventory feed is configured with. These contracts are the only published description of the API surface:
  no OpenAPI, Swagger, GraphQL SDL or AsyncAPI document exists on any Aramisauto or Aramis Group host,
  and the API vhost itself is credential-gated.'
humanURL: https://schemas.aramis.group/
baseURL: https://api.aramisauto.com
tags:
- Vehicle Data
- Catalog
- Search
- Marketplace
- JSON-Schema
tags_raw:
- Vehicle Data
- Catalog
- Search
- Marketplace
- JSON Schema
properties:
- type: JSONSchema
  url: json-schema/_index.yml
- type: Examples
  url: examples/_index.yml
- type: Vocabulary
  url: vocabulary/aramisauto-vocabulary.yml
- type: DataModel
  url: data-model/aramisauto-data-model.yml
- type: Conventions
  url: conventions/aramisauto-conventions.yml
- type: Conformance
  url: conformance/aramisauto-conformance.yml
- type: RateLimits
  url: rate-limits/aramisauto-rate-limits.yml
- type: SchemaRegistry
  url: https://schemas.aramis.group/
- type: SourceCode
  url: https://github.com/ARAMISAUTO/schemas.aramis.group
x-evidence:
  fetched: '2026-08-17'
  schemas:
    url: https://schemas.aramis.group/
    http_status: 200
    documents: 10
    examples: 5
    all_parse: true
    draft: 2020-12
  ownership: The contracts are served from aramis.group, not aramisauto.com. Aramis Group SA is the listed
    parent that operates the Aramisauto brand in France, the site titles itself "Aramis Group Schemas",
    and the repository behind it (github.com/ARAMISAUTO/schemas.aramis.group, CNAME schemas.aramis.group)
    belongs to the GitHub organisation "Aramisauto.com" whose profile blog is https://www.aramisauto.com.
    The field names are Aramisauto-specific — aramisautoSupplierId, aramisautoPickupPointId, aramisautoSimpleColor,
    aramisautoCategory, aramisautoBodywork, aramisautoEnergyType, aramisautoSellingPriceWithTaxes — so
    these are this company's contracts, not a sibling brand's.
  base_url_probe:
    url: https://api.aramisauto.com/
    http_status: 403
    content_type: application/xml; charset=utf-8
    body: <?xml version="1.0" encoding="utf-8"?><Errors><Error><Message>Missing WSSE Username.</Message></Error></Errors>
    headers:
      x-vhostid: api
      x-aramisauto-application: api
    note: 'The host is real and is the group''s API application vhost, but it is opaque: a control path
      that cannot exist returns the IDENTICAL 403, so the gate sits in front of routing and no individual
      endpoint can be confirmed from anonymous probing. baseURL is recorded as the bare host for that
      reason — no path is asserted. No public document ties a named path on this host to the published
      catalog schemas, so that join is deliberately not claimed.'
  spec_discovery:
    openapi: none
    note: Probed /openapi.json, /openapi.yaml, /swagger.json, /v1/openapi.json, /api-docs, /docs, /redoc
      and /graphql on api.aramisauto.com (blanket 403) and on www.aramisauto.com (404, with a control
      path also 404 — real negatives). developer.aramisauto.com, developers.aramisauto.com, docs.aramis.group
      and api.aramis.group do not resolve. /.well-known/agent-card.json and /.well-known/agent.json miss
      on every host. No MCP endpoint is published. The GitHub organisation contains no specification.