Support and escalation - JobHandy Developers

Use the established JobHandy customer or integration support channel for your organization. The Public API contract does not define a universal support email address, so this page does not invent one.

Before escalation

Reproduce the issue with a new X-Request-ID when safe.
Check Troubleshooting.
Confirm the OpenAPI version and endpoint path.
Re-read the resource after a write timeout or 409.
Remove secrets and unnecessary personal data from diagnostics.

Required diagnostic record

Information	Example
UTC timestamp	`2026-08-27T14:30:12.418Z`
HTTP method	`POST`
Path template	`/orders/{id}/decision`
HTTP status	`409`
API error code	`ORDER_ALREADY_DECIDED`
Request ID	`018f3d9a-7dfb-7a23-b4b4-9f7e4b19d4b4`
Tenant context	Tenant ID when relevant and permitted
Dry run	`true` or `false`
Attempts	Count and request IDs
Client version	Integration release and adopted OpenAPI version
Reproduction	Sanitized steps and expected behavior

Do not send

API keys
secret-manager screenshots
complete payroll files unless explicitly requested through an approved secure channel
unrelated incident attachments
full employee payloads when IDs and field names are sufficient
unrestricted production logs

Escalation template

Subject: JobHandy API - <operation> - <error code>

UTC time:
Environment: Public production API
Client release:
OpenAPI version:
Method and path:
HTTP status:
Error code:
Request ID:
Tenant context:
Dry run:
Expected result:
Actual result:
Reproduction steps:
Retries or reconciliation already performed:
Sanitized evidence attached:

For ambiguous write outcomes, do not create a second mutation merely to obtain a clearer error. Re-read the resource and include both the write and reconciliation request IDs.

Last modified on August 27, 2026