Explore our machine-readable API contract, typed endpoints, structured errors, and practical quickstarts for agents and application developers.
OpenAPI 3.1 schemas, unique operation IDs, response types, and recovery-ready JSON errors for agent and application integrations.
Use server-issued bearer credentials with the versioned API. Anonymous website forms remain restricted to same-origin browser requests.
Contact our team for higher-volume access, rate-limit guidance, webhooks, MCP integrations, API keys, or sandbox requirements.
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 --fail-with-body \
-H "Authorization: Bearer $ZAKCODEX_API_TOKEN" \
-H "Accept: application/json" \
https://zakcodex.com/api/v1/phone-countrySend 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 --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"}'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.