Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.anchorbrowser.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Common use cases

Use caseDescription
Internal servicesAccess private dashboards and endpoints using certificates signed by your organization’s CA
Dev/staging environmentsConnect to environments with self-signed or private CA certificates
mTLS authenticationValidate server certificate chains in mutual TLS setups
QA/testingRun automated tests with temporary CAs or simulated certificate chains
Enterprise networksSupport environments with custom trust policies or air-gapped infrastructure

​
Managing certificates

Certificates are managed at the team level. Upload a certificate once, then reference it by name in any session.

​
Upload a certificate

curl -X POST https://api.anchorbrowser.io/v1/certificates \
  -H "anchor-api-key: YOUR_API_KEY" \
  -F "file=@/path/to/your-ca.crt" \
  -F "name=my-internal-ca" \
  -F "description=CA for internal services"
ParameterRequiredDescription
fileYesCertificate file (.crt, .pem, .cer, .der)
nameYesUnique identifier (alphanumeric, hyphens, underscores)
descriptionNoOptional description (max 1000 characters)

​
List certificates

curl https://api.anchorbrowser.io/v1/certificates \
  -H "anchor-api-key: YOUR_API_KEY"

​
Delete a certificate

curl -X DELETE https://api.anchorbrowser.io/v1/certificates/my-internal-ca \
  -H "anchor-api-key: YOUR_API_KEY"

​
Using a certificate

After uploading a certificate, reference it by name when creating a session: 
curl -X POST https://api.anchorbrowser.io/v1/sessions \
  -H "anchor-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "browser": {
      "ca_cert": {
        "active": true,
        "name": "my-internal-ca"
      }
    }
  }'

Proxy

Route traffic through proxies for network control.

Authentication

Persistent identity for seamless access to applications.