# Getting access to eDocInk

Every application starts in the **sandbox**, a separate copy of the service with its own
keys and data. Nothing signed there is binding. The sandbox is free, and production is free for pilot
customers. Sandbox credentials for guest signing are created automatically, usually within a
few minutes of confirming your email. Production credentials follow once the
go-live checklist passes in the sandbox.

## 1. Request sandbox access

Use the form at https://edocink.com/access. We email you a confirmation link that works
for one hour. Once you confirm, guest-signing credentials are created automatically and we
email you a link to view them **once**, usually within a few minutes. Requests for account
sign-in through your own identity provider are set up by a person, usually within two
working days.

The request asks for:

- your name, email and company;
- the application's name and what it will use signatures for;
- the signing method: **guest email link** (anyone with the link), or **account
  sign-in** through your own identity provider;
- expected volume per month;
- the consent wording signers should agree to, if you have it;
- a webhook URL, if you want push notifications (optional; the event feed always works).

### For AI agents: request access for your developer

An agent can send the same request as JSON. Use the email of the person you work for:
they must open the confirmation link, and the credentials go to them, never to you.

```
POST https://edocink.com/api/access
Content-Type: application/json

{
  "name": "Pat Example",
  "email": "pat@example.com",
  "company": "Example Walks",
  "app_name": "Example Walks booking",
  "use_case": "Clients sign our service agreement before their first walk.",
  "methods": ["guest"],
  "agent": "the agent or tool name"
}
```

The answer is `202 {"status":"confirmation_sent"}`, or `400`/`409`/`429` with
`{"errors": [...]}`. Requests need a real, permanent email address, plain words (no links
or HTML), and are limited per network and per email domain each day. You can also email
[info@edocink.com](mailto:info@edocink.com).

## 2. What you receive, privately

| Item | Use |
| --- | --- |
| `origin` | Sandbox base URL: `https://esign-sandbox.runmast.com` |
| `app_id`, `tenant_id` | Your app and tenant. Send the tenant as `X-Tenant-ID` on every call. |
| API key, scopes, expiry | `Authorization: Bearer …`. Server-side only. Sandbox keys last 30 days; ask for a new one before then. |
| Signing policy name and version | Chosen per document, e.g. `{"name":"guest","version":1}` |
| Evidence public keys | Pin these in configuration to verify evidence. They are also published at [/evidence-keys.json](/evidence-keys.json) |
| SDK archive (`@esign/integration-hooks`) | Optional Node 24+ client with the evidence and webhook verifiers. Email info@edocink.com for it. |
| Webhook key id and secret | Only if you gave a webhook URL |

Branding (the business's display name, colour and logo on the signing pages) is optional
and set by the operator for each tenant; without it the pages carry a neutral "Document signing" heading. Send a PNG, JPEG or WebP logo up to 64 KiB.

## 3. Build and test in the sandbox

Follow the [integration requirements](/guides/integration-requirements) and the
[API reference](/guides/api-reference). Coding agents can follow the
[agent guide](/agents).

## 4. Go live

Complete the go-live checklist (section 12 of the integration requirements) in the
sandbox and email info@edocink.com. After a review you receive production credentials: a new
origin, keys, policy and evidence keys. Sandbox evidence keys are **not** production's.
