Home / Certified translation API

Certified Translation API

Q: How do I authenticate?

Send your key as Authorization: Bearer <key> or X-API-Key: <key> . Keys are issued by eVerbary, tied to an account, stored only as SHA-256 hashes, and revoked at once if one leaks.

Q: How do I avoid duplicate orders on a retry?

Send an Idempotency-Key header when you create an order. A retry with the same key returns the first order instead of placing a second one.

Q: How do webhooks work?

Register an HTTPS URL with PUT /v1/webhook and keep the signing secret it returns. Every status change of an API order is posted to it with an X-Everbary-Signature header (HMAC-SHA256 over the timestamp and the raw body). Failed deliveries are retried five times over about two hours.

Q: Can I put my client's name and case number on the order?

Yes. client_first_name , client_last_name and case_number go on the order, and the case number is printed on the invoice.

The eVerbary Order API lets your software place certified translation orders with the documents attached, follow each order's status and download the finished translation, with webhooks that report every status change. An API order is an ordinary eVerbary order: same $24.95 per page, same team discount and billing terms, same signed certification. The reference documentation is at orders.everbary.com/v1/docs.

Create Order — $24.95/page Free Quote

REST + webhooks

Multipart uploads, JSON responses, HMAC-SHA256 signed callbacks.

Your account, your terms

Team discount, invoicing and payment links apply as on the website.

Keys on request

Write to support@everbary.com. Stored as hashes; revoked at once.

Endpoints

Base URL https://orders.everbary.com. Full reference with request and response schemas: orders.everbary.com/v1/docs.

eVerbary Order API endpoints
Endpoint	What it does
`POST /v1/orders`	Places an order: the files (multipart), the language pair, the page count, and optionally expedited, Expedited Plus, notarization, your client's name, a case number and a reference. Returns the order number and price; accounts that pay per order also get a payment link.
`GET /v1/orders/{orderNumber}`	Status, expected delivery, payment and invoice, and the certified translation files once delivered.
`POST /v1/orders/{orderNumber}/send-payment-link`	Emails the order's payment link to whoever should pay, for example your client.
`GET /v1/languages`	The language codes the order form accepts.
`GET /v1/turnaround`	Delivery estimates for a page count on each service level, as the website quotes them.
`GET /v1/expedited-plus`	Whether Expedited Plus can be ordered now for a language pair (8:00 AM to 4:59 PM Eastern, 22 languages).
`PUT /v1/webhook`	Registers the HTTPS URL that receives status changes and returns its signing secret, once.
`GET /v1/health`	Service health, no key needed.

Placing an order

A minimal request, with your key and an idempotency key:

curl https://orders.everbary.com/v1/orders \
  -H "Authorization: Bearer $EVERBARY_KEY" \
  -H "Idempotency-Key: matter-1234-birth-cert" \
  -F email=paralegal@yourfirm.com -F first_name=Ana -F last_name=Diaz \
  -F language_from=spanish -F language_to=english -F pages=1 \
  -F client_first_name=Maria -F client_last_name=Lopez -F case_number=A-123 \
  -F files=@birth-certificate.pdf

Webhooks

Register one HTTPS URL per key. Each delivery carries X-Everbary-Signature: t=<unix time>,v1=<hex>, an HMAC-SHA256 of "<t>.<raw body>" with your signing secret. Verify it and reject old timestamps: the URL is on the open internet and the signature is how you know the call is ours. A failed delivery is retried five times over about two hours; the current status is always available from GET /v1/orders/{orderNumber}.

Keys, scope and limits

Keys are issued by eVerbary on request (support@everbary.com) and belong to an account: orders are placed under it, priced with its team discount and billed on its terms.
Keys are stored only as SHA-256 hashes. A lost key is revoked, not recovered.
A key reads only its own account's orders; any other order number answers "not found".
HTTPS only. Send Authorization: Bearer or X-API-Key, whichever your platform supports.

What the API does not do yet

There is no sandbox: test orders are real orders with real invoices. Tell us before you start testing.
Orders cannot be cancelled or revised through the API; use the order page or write to us.
Mailed hard copies are ordered on the website.

Rather use an AI assistant?

The same account can be used from Claude, ChatGPT, Cursor or VS Code through our MCP server; see AI assistants.

Frequently asked questions

Is there a sandbox for testing?

Not yet. Orders placed through the API are real orders with real invoices, so tell us at support@everbary.com before you start testing and we will work it out with you.

How are API orders priced?

Exactly as on the website: $24.95 per page of up to 250 words, Expedited +20%, Expedited Plus +40%, notarization $34.90 per order, with your team's discount applied to the page price.

How do I authenticate?

Send your key as Authorization: Bearer <key> or X-API-Key: <key>. Keys are issued by eVerbary, tied to an account, stored only as SHA-256 hashes, and revoked at once if one leaks.

How do I avoid duplicate orders on a retry?

Send an Idempotency-Key header when you create an order. A retry with the same key returns the first order instead of placing a second one.

How do webhooks work?

Register an HTTPS URL with PUT /v1/webhook and keep the signing secret it returns. Every status change of an API order is posted to it with an X-Everbary-Signature header (HMAC-SHA256 over the timestamp and the raw body). Failed deliveries are retried five times over about two hours.

Can I put my client's name and case number on the order?

Yes. client_first_name, client_last_name and case_number go on the order, and the case number is printed on the invoice.

Can the API order mailed hard copies?

No. Hard copies need a shipping address and are ordered on the website.

Ask for a key

Write to support@everbary.com with the account email the key should belong to.