Anatomy of a URL

The various segments of the AuvProxy URL allow you to define complex and custom proxy behaviors.

The URL scheme allows Auric to mix and match functionality for more advanced and custom solutions. For example, it is possible to both detokenize a request and tokenize the responses. This is useful, for example, if you want to tokenize the credentials you use to access a remote service.

URL Segments

The following segments comprise AuvProxy URL:

/<Version>/<Request Action>/<Response Action>/<Destination Source>/<AccessID>


Always v1, indicating this is the first version of the proxy interface.

Request Action

Which modification to make to the HTTP Request body sent to the proxy before the proxy forwards it to the target web service:

  • pass (do nothing)

  • tokenize

  • detokenize

Response Action

Which modification to make to the HTTP Response body received from the target web service before returning it:

  • pass (do nothing)

  • tokenize

  • detokenize

Destination Source

Tells the proxy where to find the URL to which to forward the request. The standard value is hdr, indicating the target URL is in the X-AUV-PROXY-DEST HTTP header.

The proxy uses any other value than hdr to lookup a pre-configured destination. This feature is useful when third-parties are pushing data through the proxy into your environment. By giving the third party a customized URL, the proxy can properly redirect the traffic without the use of the X-AUV-PROXY-DEST HTTP header.

This feature can also be used if you have a software library incapable of adding an HTTP header – typically some legacy application that cannot be modified.


The AccessID identifies your account to the AuvProxy service. Firewall rules lock down access to the production AuvProxy web service. The combination of your IP address and AccessID identifies your valid account.

Note: You are issued separate AccessID values for the sandbox (test) and production environments.