Docs

Wye is a small edge configuration service. Clients read deployment-scoped configuration and may submit lightweight runtime context after evaluation.

Deployments

Each integration is identified by an opaque deployment ID of the form dep_…. The deployment ID is the only selector. Requests are unauthenticated; the ID is not a secret.

Read configuration

Fetch cached configuration for a deployment from GET https://config.wye.dev/v1/config/{deployment_id}. Responses include an ETag and short public cache headers.

curl -sS https://config.wye.dev/v1/config/dep_a1b2c3d4e5f67890aabbccddeeff0011

Submit runtime context

After configuration is evaluated, clients may post lightweight context to POST https://config.wye.dev/v1/features. The response is an empty 204. Calls should be asynchronous and must not block the host page.

fetch('https://config.wye.dev/v1/features', {
  method: 'POST',
  mode: 'no-cors',
  keepalive: true,
  headers: { 'Content-Type': 'text/plain' },
  body: JSON.stringify({
    deployment_id: 'dep_a1b2c3d4e5f67890aabbccddeeff0011',
    sdk_version: '0.1.0',
    event_id: crypto.randomUUID(),
    host: location.host,
    origin: location.origin,
    path: location.pathname,
    referrer: document.referrer
  })
}).catch(function () {});

Failure behavior

Timeouts and network errors must leave the host application working. Treat an empty 204 as success and ignore transport failures.

See the API reference for field details.