API · /dotenv-api

Dotenv API

healthy 3,653 Subscribers

Convert between .env (dotenv) files and JSON, in both directions. The parse endpoint reads .env text into a clean JSON object: it skips blank lines and # comments, honours an optional leading export, unquotes single- and double-quoted values (interpreting \n, \t and \" escapes inside double quotes), strips inline comments after unquoted values, supports values that span several lines inside quotes, and can optionally expand ${VAR} and $VAR references against the variables already defined earlier in the same file — while leaving single-quoted values strictly literal. The stringify endpoint turns a JSON object back into a valid .env file, quoting only the values that actually need it and optionally prefixing every line with export for shell sourcing. Everything is computed locally and deterministically, so it is instant and private — your secrets never leave the request. Ideal for config tooling and migrations, CI/CD pipelines, converting .env to JSON for apps that want structured config (and back), and validating environment files. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This handles the dotenv format; for INI files with [sections] use an INI API, and for YAML or TOML use those APIs.

api.oanor.com/dotenv-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/dotenv-api/openapi.json
/api/dotenv-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
79 ms
Server probes · 24h
Subscribers
3,653
active
Total calls
36
last 7 days
status Full status page → · 6 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 4,235 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 4,235 calls/month
  • 2 req/sec
  • Parse + stringify
  • No credit card
Sign in to subscribe

Starter

€5.75 /month

  • 13,750 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 13.75k calls/month
  • 8 req/sec
  • Quotes, comments, ${VAR} expansion
  • Email support
Sign in to subscribe

Pro

€25.65 /month

  • 188,500 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 188.5k calls/month
  • 20 req/sec
  • Config / CI/CD pipelines
  • Priority support
Sign in to subscribe

Mega

€63.65 /month

  • 985,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 985k calls/month
  • 50 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

Related APIs

Other APIs with overlapping tags.

JSON Merge API

Deep-merge JSON objects — the operation every config and settings system needs. The merge endpoint recursively merges two objects (the second overrides the first), or a whole list of objects merged left-to-right, combining nested objects key by key rather than replacing them wholesale, with a choice of array strategy: replace (default), concat, union (concatenate and de-duplicate) or merge_index (merge element by element). A null in the overriding object can either overwrite the existing value or be ignored, so you can patch only the fields you mean to. The defaults endpoint is the inverse and just as useful: it fills in only the keys your data is missing from a defaults object, so your existing values always win — exactly how you layer a user's settings over default configuration. Everything is computed locally and deterministically, with no schema required. Ideal for configuration and feature-flag layering, settings and preference merges, combining API responses or partial updates, environment overrides, and template defaults. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This merges documents; to diff or patch them (RFC 6902) use a JSON-diff API, to flatten them use a flatten API, and to address values use a JSON-Pointer API.

api.oanor.com/jsonmerge-api

INI API

Convert between INI configuration files and JSON, in both directions. The parse endpoint reads INI text — sections ([section]), nested sections ([database.replica]), key=value pairs, comments and repeated keys (arrays) — into a clean JSON object; the stringify endpoint turns a JSON object back into a properly formatted INI file. INI is the config format used by Git (.gitconfig), PHP (php.ini), systemd units, desktop entries, tox/setup.cfg, many CLI tools and Windows software. Perfect for editing config programmatically, migrating settings between formats, and reading config in environments that only speak JSON. Pure local computation — no key, no third-party service, instant; send large files via POST. Live, nothing stored. 3 endpoints. Complements the YAML, TOML, CSV and XML converters and is distinct from each.

api.oanor.com/ini-api

TOML API

Convert and validate TOML — the config format behind Cargo.toml, pyproject.toml, Netlify and many tools. Turn TOML into JSON, turn JSON back into clean spec-compliant TOML 1.0, and validate any TOML with a precise error message (line and column) when it is malformed. Tables, arrays of tables, inline tables, typed values and datetimes are all handled. Input via the query string or the request body (up to 4 MB). Pure local processing — no key, no third-party service, instant. Live. 4 endpoints. Completes the oanor config-format family alongside the JSON, YAML, XML and CSV APIs — built for build tooling, config editors, CI and data pipelines.

api.oanor.com/toml-api

YAML API

Convert, validate and tidy YAML through a fast, fully-local API. Turn YAML into JSON (including multi-document streams) or JSON into clean YAML with optional key sorting and custom indentation, validate a document and get the exact line and column of any syntax error with a context snippet, or reformat and normalize existing YAML. Inputs can be sent as a raw text/plain body, a JSON field or a query parameter; outputs are tidy JSON. Pure server-side compute with no third-party upstream, so responses are instant and the service is always available. Ideal for DevOps and CI/CD, configuration and infrastructure-as-code tooling, no-code platforms, editors and data pipelines.

api.oanor.com/yaml-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Dotenv API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Dotenv API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Dotenv API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Dotenv API cost?
Dotenv API has a free tier with 100 calls / month. Paid plans start at €5.75 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Dotenv API GDPR-compliant?
All requests to Dotenv API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/dotenv-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/dotenv-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/dotenv-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/dotenv-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.