Endpoints
Every integration reaches revenexx through a small set of public hostnames. All of them are HTTPS-only. Which ones the edge fronts and which the origin answers directly is not cosmetic — it decides where TLS terminates, what caching you get, and where the request is filtered.
| Hostname | Answered by | What it is for |
|---|---|---|
https://api.revenexx.com/v1 | The origin, in Germany | Every API call |
https://<tenant>.revenexx.cloud | The nearest point of presence | The domain every tenant gets on creation |
| Your own domain (CNAME to the edge) | The nearest point of presence | Storefronts, themes, and /cdn/ asset paths |
Every tenant is given <tenant>.revenexx.cloud when it is created, already pointed at the edge and already known to the mail service. So a new tenant can serve assets and send mail before anyone has touched DNS. Connecting your own domain adds a second name for the same thing; it does not replace it.
API gateway
All API calls go to a single entry point, versioned under /v1:
https://api.revenexx.com/v1
This is the base URL you set in every SDK and use for direct REST calls. Requests are scoped to a tenant with the X-Revenexx-Tenant header, so there is no per-region host and no per-tenant host to look up. The conventions that apply to every call — headers, credentials, request IDs, errors — are in API usage.
curl -i https://api.revenexx.com/v1/products \
-H "X-Revenexx-Tenant: <TENANT_SLUG>" \
-H "X-Revenexx-Api-Key: rvxk_..."
The gateway is answered by the origin, not by a point of presence. Its throughput is governed by the per-tenant rate limits, and cacheable capability responses are served from the gateway's own response cache — see Caching.
The tenant's OpenAPI description is available at https://api.revenexx.com/v1/openapi.json, and rendered in the API Explorer.
Storage delivery
Files you store in revenexx Storage are read and transformed under the /cdn/ path of a domain you have pointed at the edge:
https://shop.example.com/cdn/<folder>/<file>
The path after /cdn/ is the path inside your tenant's storage — the domain already identifies the tenant, so there is nothing else to put in the URL. Public assets need no credential; private ones need a signed URL. Image transform parameters go on the same URL:
https://shop.example.com/cdn/photos/sunset.jpg?w=800&fm=webp
These requests are answered by the nearest point of presence, so a transformed variant is generated once and served from the edge after that — see Content delivery.
See Storage for upload and download, and Serve and transform images for the full transform parameter list.
Your own domains
A domain you own can serve your storefront and your assets. It needs one DNS record — a CNAME pointing at the edge hostname Cockpit shows you — after which the nearest point of presence fronts it, terminates TLS with a certificate issued for you, and caches what is cacheable.
shop.example.com. 3600 IN CNAME edge.revenexx.com.
Copy the value from Cockpit rather than from this page. The edge hostname is configuration and can change; the DNS & TLS view of the domain always shows the current one.
There is no domain API. Domains are added and verified in Cockpit, and the endpoints for doing it are not exposed on the public gateway — so plan for that step to be done once by a human. Domains covers the record types, apex domains, CAA records, and verification troubleshooting.
Related
- Edge network — the four points of presence and the origin behind them
- API usage — headers, credentials, and response conventions for every call
- Content delivery — what the edge does for a domain you point at it