Developer Resources

ZakCodeX Developer Portal

Documentation and quickstarts for building with the ZakCodeX API.

Developer workspace with code displayed across multiple monitors

Build with ZakCodeX

Developer resources for reliable integrations

Explore our machine-readable API contract, typed endpoints, structured errors, and practical quickstarts for agents and application developers.

Typed API contract

OpenAPI 3.1 schemas, unique operation IDs, response types, and recovery-ready JSON errors for agent and application integrations.

Protected endpoints

Use server-issued bearer credentials with the versioned API. Anonymous website forms remain restricted to same-origin browser requests.

Integration support

Contact our team for higher-volume access, rate-limit guidance, webhooks, MCP integrations, API keys, or sandbox requirements.

Public utility

Resolve a country suggestion

Use the authenticated country utility to select a sensible telephone input default based on the request context, with an explicit fallback when location data is unavailable.

cURL
curl --fail-with-body \
  -H "Authorization: Bearer $ZAKCODEX_API_TOKEN" \
  -H "Accept: application/json" \
  https://zakcodex.com/api/v1/phone-country

Project enquiries

Submit an enquiry

Send clearly identified test data only and avoid personal or sensitive information during integration checks. A successful submission creates a real project enquiry for the ZakCodeX team.

cURL
curl --fail-with-body \
  -X POST https://zakcodex.com/api/v1/contact-submissions \
  -H "Authorization: Bearer $ZAKCODEX_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name":"Agent Test","email":"agent@example.com","message":"Integration enquiry"}'

Access and support

Authentication, errors, and sandbox access

All documented versioned API endpoints require a server-issued bearer token. Tokens must never be embedded in browser JavaScript or public repositories.

A separate sandbox host and self-service API keys are not currently published. Error responses include error.code, error.message, and error.hint so integrations can recover predictably.