<!-- /access.md -->

# Get access

Start with the test API, which needs no account. A connection to a dealership is switched on by the dealership.

**Test API: One lead**

```bash
curl "https://developer.architera.ai/sandbox/leads" \
  -H "Authorization: Bearer alk_test_public_sandbox"
```

**Test API: Empty**

```bash
curl "https://developer.architera.ai/sandbox/leads?simulate=empty" \
  -H "Authorization: Bearer alk_test_public_sandbox"
```

**Test API: 401**

```bash
curl "https://developer.architera.ai/sandbox/leads?simulate=401" \
  -H "Authorization: Bearer alk_test_public_sandbox"
```

**Test API: 429**

```bash
curl "https://developer.architera.ai/sandbox/leads?simulate=429" \
  -H "Authorization: Bearer alk_test_public_sandbox"
```

## Try it today

The test API returns a fictional lead and checks a signed one. Its key and secret are public and work nowhere else. See [Test data and simulations](/connections/https-webhook#w-test).

## Production

Production HTTPS transport supports a configured API-key header, bearer or basic credential, or its configured no-auth mode, and Standard Webhooks signing when configured with a destination signing secret. This portal does not issue those private credentials.

Confirm the actual destination, deployment and private authentication/signing configuration with the dealership before real leads flow. The public test secret must never protect real data; do not disable verification to accept a delivery.

## Ask for a connection

Every connection is available on request and activated per dealer. Tell us the system, the dealership and what you need it to do.

[Write to accounts@architera.ai](mailto:accounts@architera.ai?subject=Developer%20portal%3A%20connection%20request)

## Support

Support is best effort, and the founders respond. Quote the request id from any error you report.
