Troubleshooting
Common issues and solutions when using the Vine Public Content API
This guide covers the most common integration problems with the current shipped Vine public API.
Invalid API Key (401 Unauthorized)
What you see:
{
"ok": false,
"error": "Invalid API key"
}Status Code: 401 Unauthorized
Possible causes:
- the API key is incorrect
- the API key was deleted or revoked
- the key was copied with extra spaces
Solutions:
- Verify that you copied the exact API key from Vine.
- Make sure the key is in the path, not in a header.
- Remove any leading or trailing spaces.
Example:
# Wrong
curl "https://vinecms.tech/api/public/v1/posts"
# Correct
curl "https://vinecms.tech/api/public/v1/{API_KEY}/posts"Missing API Key (401 Unauthorized)
What you see:
{
"ok": false,
"error": "Missing API key"
}Status Code: 401 Unauthorized
Cause:
- the route is missing the
:apiKeysegment
Post Not Found (404 Not Found)
What you see:
{
"ok": false,
"error": "Post not found"
}Status Code: 404 Not Found
Possible causes:
- the slug is wrong
- the post is still a draft
- the post is hidden
- the post was deleted
Solutions:
- Verify the slug in Vine.
- Make sure the post is
published. - Make sure the post is
visible. - Use the list endpoint first to confirm the slug.
curl "https://vinecms.tech/api/public/v1/{API_KEY}/posts"Empty Post List
What you see:
{
"ok": true,
"posts": []
}Possible causes:
- there are no posts in the workspace
- all posts are drafts
- all posts are hidden
Current rule:
Only posts with:
status = "published"visible = true
are returned.
Wrong Route Shape
The current route format is:
/api/public/v1/{API_KEY}/postsIf you are calling an older route format, update it.
Expecting Pagination Or Filters
The current shipped API does not yet support:
limitoffset- category filtering
- tag filtering
- author filtering
- search
If you used older docs that mentioned those features, those docs were ahead of the implementation.
Health Checks
Use these routes to verify that the service itself is up:
curl "https://vinecms.tech/api/health"
curl "https://vinecms.tech/api/public/v1/status"Response Shape Mismatch
If your integration expects older data envelopes such as:
{
"data": []
}update it to the current Vine response format:
{
"ok": true,
"posts": []
}