Built for real product teams

Useful APIs, without the integration sprawl.

Actoki gives developers one clear way to work with maps, verification and everyday data tasks.

REST and JSON Server-side security controls Human support
Actoki workspace
Platform overviewOperational
Services53
Endpoints272
AccessScoped
ServiceStatusUsage
Maps APIEnabledHealthy
Domain GuardEnabledHealthy
Travel toolsScopedReady
53service families in the installed catalogue
272documented endpoint definitions
One accountfor credentials, permissions and usage
Clear controlsfor keys, access, maps and audit history
The platform

Choose the capability, keep the same developer experience.

The catalogue is broad by design, but the experience is deliberately consistent: familiar authentication, structured responses, predictable errors and one place to manage access.

Maps & location

Protected maps, plotting, styles, geocoding, address tools and geographic utilities for customer-facing products.

View documentation

Verification & trust

Email, domain, phone, identity and risk checks that help teams make cleaner decisions at the point of entry.

View documentation

Travel intelligence

Airport, country, timezone, currency, weather and practical travel-rule endpoints for travel workflows.

View documentation

Data & documents

Transform structured data, extract useful information and automate repetitive document-processing tasks.

View documentation

Security & monitoring

Security-header checks, domain health, website monitoring, privacy scans and operational alerts.

View documentation

Business utilities

Finance, content, marketing, accessibility and developer tools that remove small but costly integration work.

View documentation
Developer experience

A sensible first request, then room to grow.

The quick-start path is intentionally small. Keep the key on your server, send a normal HTTP request and receive a structured response you can log and handle.

01

One authentication pattern

Use an API key from a trusted server environment and scope access to the services your application actually needs.

02

Errors built for software and people

HTTP status codes and stable JSON errors make failures easier to diagnose without turning support into archaeology.

03

Usage you can explain

Endpoint-level metering and account controls help technical and commercial teams understand what the product is doing.

# Keep the key in a server-side environment variable
curl --request POST \
  --url https://actoki.com/v1/domain-guard/check \
  --header "Authorization: Bearer $ACTOKI_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"domain":"example.org"}'
Maps without careless key exposure

Customer-facing maps with server-side control.

Create routes, pins and boundaries while keeping permanent credentials out of browser code. Use short-lived tokens or protected embeds, restrict origins and monitor usage.

StartDestination
Protected map sessionShort-lived browser token · exact origin · scoped map access

Designed to reduce avoidable abuse

Security is strongest when several small controls reinforce one another.

Permanent keys stay server-sideDo not ship reusable account secrets in JavaScript, mobile bundles or public repositories.
Browser access is temporary and narrowIssue short-lived map credentials with only the region, style and features needed for the current session.
Origins and permissions are explicitRestrict approved sites and avoid permissive wildcard rules for production customer domains.
Usage is monitored and revocableSet sensible caps, review anomalies and rotate or revoke credentials when ownership changes.
Read the protected maps guide
Security that supports the product

Strong defaults, visible controls and no mystery theatre.

Actoki combines account security, API controls and operational safeguards. The documentation explains what developers should do without publishing sensitive detection logic or pretending any system is risk-free.

API key lifecycleCreate, scope, rotate and revoke credentials.
Rate limitingControl bursts and protect shared capacity.
Two-factor authenticationAdditional protection for account access.
Audit historyReview administrative and key events.
Protected mapsShort-lived tokens and origin restrictions.
Production headersCSP, frame, referrer and browser controls.
A straightforward path

From evaluation to a production integration.

Good onboarding should make the next decision obvious without forcing a sales conversation before a developer can learn anything.

1

Explore the catalogue

Read the guides, search the endpoint reference and decide which services match the product problem you are actually solving.

2

Test safely

Create a developer account, keep credentials in a trusted environment and validate requests against non-sensitive data first.

3

Harden and launch

Restrict access, add timeouts and retries, monitor usage and complete the production checklist before customer traffic arrives.

Frequently asked questions

Answers before you need a meeting.

These are the practical questions teams usually ask while evaluating an API platform. The docs go deeper, and support is there when the answer depends on your implementation.

Open the documentation
What can I build with Actoki?
Actoki brings maps, email and domain verification, travel data, document tools, monitoring, security checks and practical developer utilities behind one consistent account. You can use a single service or combine several in the same product.
How quickly can a developer get started?
Create an account, generate an API key and make a first authenticated request from the quick-start guide. The documentation includes cURL, Node.js and PHP examples, clear error handling and a searchable endpoint reference.
Can I expose an API key in browser JavaScript?
Permanent secret keys should stay on your server. For browser maps, use short-lived map tokens or protected embeds with origin restrictions, narrow permissions and usage controls. The maps guide explains the safer patterns.
How are usage and costs controlled?
Requests are metered at endpoint level. Account administrators can review usage, permissions and service access from the dashboard, while rate limits and server-side controls help prevent unexpected bursts and misuse.
Do I have to use every API service?
No. Services can be enabled for the accounts that need them. This keeps the platform focused, reduces unnecessary access and lets teams expand their integration over time.
What happens when an API request fails?
The APIs return structured JSON errors with an HTTP status, a stable error code and a human-readable message. Retry only transient failures, respect Retry-After where supplied and use idempotency for operations that may be repeated.
Is Actoki suitable for production workloads?
The platform includes API-key controls, rate limiting, audit trails, security headers, two-factor authentication and protected map delivery. Production deployment still requires correct secrets, TLS, backups, monitoring and staging tests for your own environment.
Can I speak to a person before integrating?
Yes. The support route is available for product, onboarding and implementation questions. The goal is to help your team choose a sensible integration, not to push unnecessary services.

Start with the API your product needs.

Explore the reference, create an account when you are ready and build the first request without a lengthy procurement dance.

Create a developer account