Get one useful thing working before you configure everything.
Start with one real product question. Specky helps you turn it into something you can review.
Try saying
“Here is what we are hearing from customers. What is the clearest problem to solve first?”
Bring one thing
A product URL, note, or customer quote.
Ask clearly
Say what you are trying to decide.
Review together
Check the evidence before you act.
Specky API versioning and deprecation policy
Versioning
The Specky REST API is versioned in the URL. The current version is /api/v1, which is in beta.
What changes without a new version
New endpoints, new optional parameters, new response fields, and new error codes can arrive at any time. Write clients that ignore fields they do not recognize.
What counts as breaking
Removing or renaming an endpoint or field, changing a field's type, or adding a required parameter is a breaking change. Breaking changes go into a new version.
How much notice you get
A deprecated version or endpoint keeps working for at least 90 days after we announce it. We announce it in the changelog.
How to detect a deprecation
While something is on its way out, its responses carry these headers:
| Header | Meaning |
|---|---|
Deprecation | When it was deprecated (RFC 9745) |
Sunset | When it stops working (RFC 8594) |
Link with rel="deprecation" | Where to read about the replacement |
Nothing is deprecated today, so you will not see these headers yet.
Ready to apply this?
Start with your own product and keep the first read grounded. You'll create an account before the guided result so it can be saved to your workspace.