Skip to main content
Most upstream APIs require credentials. Proceeds attaches those credentials to the proxied request on the server side, so your end users only see the Proceeds URL — never your bearer token, API key, or secret.

​
Pick an auth method

Configure auth at the service level. Every paywall in the service inherits it.

​
What Proceeds collects

Depending on the method, Proceeds collects values such as:
  • Bearer token
  • Token
  • API key
  • Header name and header value
  • Parameter name and parameter value
  • Customer ID
  • API secret
  • Field name and field value
These are stored encrypted at rest and only ever sent to the upstream Target URL — never returned to clients.

​
Change credentials

Editing auth on a service rotates the credentials Proceeds sends upstream on the next request. There’s no client-side change required.
Always rotate upstream credentials in Proceeds first, then in your origin. Rotating in the wrong order will break in-flight requests.

​
Next

Custom headers and query parameters

Forward extra headers or query params on a per-paywall basis.