List storefront origins
List the browser origins registered for publishable-key storefront calls.
/storefront/originsList the browser origins registered for publishable-key storefront calls.
Related endpoints
GET /storefront/products— List storefront productsGET /storefront/products/{productId}— Get a storefront productPOST /storefront/origins— Register a storefront originDELETE /storefront/origins/{originId}— Remove a storefront originGET /storefront/status— Get storefront integration status
Common errors
401 authentication_error— missing, invalid, expired, or revoked credential. Codes:authentication_failed,invalid_api_key,expired_api_key,api_key_revoked,session_invalid,merchant_required. Carries aWWW-Authenticate: Bearerchallenge.403 authorization_error— the caller is identified but the action is denied. Codes includeinsufficient_permissions,ip_not_allowed,merchant_mismatch, andorigin_not_allowed.
Pagination
Offset-based with limit (default 25, max 100) and offset. The response pagination block includes total and hasMore. See the pagination guide for SDK auto-paging helpers.
Your RevKeen merchant API key. Create and manage keys in Dashboard → Settings → Developer. Use rk_sandbox_* for staging/test and rk_live_* for production. The same key may be sent as Authorization: Bearer <key> if that suits your HTTP client better. A missing, invalid, expired, or revoked key returns 401 with a WWW-Authenticate: Bearer challenge; a valid key without the required scope returns 403.
In: header
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://api.revkeen.com/v2/storefront/origins" \
-H "x-api-key: $REVKEEN_API_KEY"Synthetic documentation data, validated against the response schema; not a live API result.
{ "data": [ { "id": "00000000-0000-4000-8000-000000000001", "object": "storefront_origin", "origin": "string", "created_at": "2026-09-01T12:00:00Z" } ]}