Start here

Quickstart

From a new account to a record answering on the internet, using the API.

Create an account and confirm your email. Sign up at itoka.ng/signup and open the link we email you.
Turn on two-factor authentication. In Settings, with an app like Google Authenticator or 1Password. Itoka asks for a code whenever you create an API key.
Get a zone. Either add a domain you own (Add a zone: publish one TXT record, then point the nameservers at Itoka), or claim a free subdomain like yourteam.itoka.dev, which is live at once.
Create an API key. Under API keys, give it a name, choose the zones and the permissions (for this guide: Read records and Write records), and copy the key. It starts with itk_live_ and is shown only once.
Make a request.

export ITOKA_API_KEY=itk_live_...

# Add a record
curl https://api.itoka.ng/api/v1/zones/yourteam.itoka.dev/records \
  -H "Authorization: Bearer $ITOKA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"record": {"type": "A", "name": "@", "value": "192.0.2.7", "ttl": 300}}'

# List the zone's records
curl https://api.itoka.ng/api/v1/zones/yourteam.itoka.dev \
  -H "Authorization: Bearer $ITOKA_API_KEY"

The write returns once both nameservers serve it: zone.replication.state is in_sync and lag_ms says how long ns2 took. Check it from your machine:

dig +short yourteam.itoka.dev @ns2.itoka.ng

DNS records: types, validation, TTLs, updating and deleting.
Webhooks: get told when anything changes.
API reference: every endpoint.

Next