Support for EdgeAssign
EdgeAssign support is currently limited and offered on a best-effort basis. This page explains where to look first, how to ask for help, and what to expect.
Support expectations
EdgeAssign is built and maintained by a solo developer. Support is available on a best-effort basis.
Documentation should be your first stop for setup and usage questions. If you still need help after checking the docs, you can reach out with the details of your issue.
Start here
Documentation
For API behavior, request format, integration guidance, and general usage, review the documentation first.
Pricing
For plan details, limits, and billing expectations, review the pricing page before reaching out.
About
For product scope, intent, and where EdgeAssign fits, see the About page.
General issues
If your issue is not answered by the site or docs, contact support with enough detail to reproduce the problem.
Contact support
For support inquiries, contact: chris.edgeassign@gmail.com
Please keep support requests focused and specific. Vague messages are much harder to investigate in a small-scale support setup.
What to include in a support request
To make it easier to investigate an issue, include as much relevant detail as you reasonably can.
- A short description of the issue
- What you expected to happen
- What happened instead
- The endpoint involved, if applicable
- The approximate timestamp of the request
- Your project ID or account email, if relevant
- Any error message or response code you received
- A minimal example request, if you can provide one safely
Common support topics
Integration questions
Questions about request format, expected behavior, endpoint usage, or deterministic assignment logic.
Billing questions
Questions about plans, limits, checkout, subscriptions, or account-level billing issues.
Unexpected responses
If an assignment or eligibility result seems incorrect, include the relevant request details and timing.
Account access issues
If you are having trouble with login or account access, include the account email and a brief description of the problem.
Before reporting a bug
Before sending a bug report, please check that the issue is not explained by request formatting, environment mismatch, account state, or plan limits.
If the issue persists, send a concise report with the most relevant reproduction details you can provide.
Security and sensitive issues
If you believe you have found a security-related issue, send a report to
chris.edgeassign@gmail.com with the subject line
Security Report.
Please include a clear description of the issue, steps to reproduce it if appropriate, and any relevant impact. Do not include exploit code, destructive payloads, or unnecessary sensitive data.
Final note
EdgeAssign is intentionally a focused, independently maintained service. The goal is to provide a clear path for legitimate product and integration issues.