Posts related to this one
Blog posts and lookbooks belong to the store’s plan: when the plan does not include them this returns 403 feature_not_available. The content is kept, and is served again as it was when the plan includes it. Posts related to the given one, ranked server-side so a storefront does not compute similarity in the browser. Read-only; accepts both publishable (tybrite_pk_*) and secret (tybrite_sk_*) API keys. Returns 404 if no published post matches the slug.
Ranking combines what the writing is about with the topics two posts share and how recent each one is, and nudges a post from a different category up between otherwise equal results.
score is diagnostic — render reason instead. The list is ordered by a rank that includes the category nudge, so the scores are not always decreasing: a post scoring 0.458 can legitimately sit above one scoring 0.511. Shown to a reader that looks like a sorting fault, whereas reason (“Closely related subject”) is something they can act on.
The list is topped up to at least three entries when few posts qualify, since a shelf of one reads as a fault rather than a short list. Topped-up entries score strictly below the weakest genuine match and carry the reason “More from this blog”.
degraded is true when the post has no stored vector yet — newly published, most often — and the ranking used topics and recency alone. The list is still returned.
curl --request GET \
--url https://api.tybritelabs.com/v1/posts/{slug}/related \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.tybritelabs.com/v1/posts/{slug}/related"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.tybritelabs.com/v1/posts/{slug}/related', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.tybritelabs.com/v1/posts/{slug}/related",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "GET",
CURLOPT_HTTPHEADER => [
"Authorization: Bearer <token>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"net/http"
"io"
)
func main() {
url := "https://api.tybritelabs.com/v1/posts/{slug}/related"
req, _ := http.NewRequest("GET", url, nil)
req.Header.Add("Authorization", "Bearer <token>")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.get("https://api.tybritelabs.com/v1/posts/{slug}/related")
.header("Authorization", "Bearer <token>")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.tybritelabs.com/v1/posts/{slug}/related")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Get.new(url)
request["Authorization"] = 'Bearer <token>'
response = http.request(request)
puts response.read_body{
"anchor": {
"id": "b47080fe-d5cd-4378-b27e-b0e849320d5b",
"slug": "top-3-premium-tech-picks-for-2026",
"title": "Top 3 Premium Tech Picks for 2026"
},
"related": [
{
"id": "13676ee0-10b8-49a0-aa3f-9afcaa02a3eb",
"title": "Building the Perfect Professional Tech Ecosystem",
"slug": "building-the-perfect-professional-tech-ecosystem",
"excerpt": "Discover how the right combination of devices can transform your productivity.",
"featured_image": "https://cdn.tybritelabs.com/posts/ecosystem.jpg",
"video": null,
"published_at": "2026-01-11T12:58:50Z",
"score": 0.4839,
"reason": "Closely related subject"
}
],
"degraded": false
}Authorizations
API Key Authentication
Use your API key in the Authorization header:
Authorization: Bearer tybrite_sk_live_YOUR_KEY
Key Types:
Secret Keys (Server-Side Only):
- Format:
tybrite_sk_live_*(production) ortybrite_sk_test_*(sandbox) - Full read/write access to all endpoints
- ⚠️ NEVER expose in client-side code or public repositories
- Required for: every write a shopper does not make for themselves, authentication, payment verification, AI recommendations
Publishable Keys (Client-Safe):
- Format:
tybrite_pk_live_*(production) ortybrite_pk_test_*(sandbox) - Catalogue reads, plus the actions a shopper takes for themselves
- ✅ Safe for client-side JavaScript, mobile apps, and public code
- Allowed for: browsing products, search, CMS content, pricing queries, cart and wishlist, reviews, storefront events, and the Agent API's quotes, cart drafts and checkout intents
Endpoint-Specific Requirements:
- Authentication endpoints (
/v1/auth/*): state-changingPOSTcalls require a secret key, for store and marketplace keys alike;GET /v1/auth/meaccepts either key - Payment verification (
POST /v1/payments/verify): Secret key required - AI Recommendations (
POST /v1/recommendations): Secret key required - Semantic Search (
POST /v1/search): Both key types allowed (read-only operation) - Shopper actions (cart, wishlist, reviews, storefront events, Agent API quotes, cart drafts and checkout intents): Both key types allowed
- All other write operations: Secret key required
- All read operations: Both key types allowed
Using a publishable key for restricted operations returns 403 Forbidden.
Limited publishable keys:
A publishable key can be limited to the products that carry one tag (for example starter:jewellery), created from
the store's Developers page. The limit applies to the key, never to the shopper: shopper sign-up and sign-in stay store-wide.
- Reads return only the slice: products (with their facets, filters, search, brands and specifications), categories and
subcategories that hold in-slice products, collections, promotions, posts and lookbooks that carry the tag, reviews of
in-slice products, prices, discovery lists and the store information summary, with every count computed on the slice.
A product outside the slice answers
404, as if it did not exist. - A write that names a product or variant outside the slice (adding to the cart or wishlist, reserving stock, an order line,
a review, a promotion calculation, a storefront event) answers
403with the error codeout_of_scope, and nothing is written or reserved. An order is refused as a whole. - A route that carries no slice behaviour is not available to the key: it answers
403withendpoint_not_allowed. - Orders placed through such a key record the tag on the order's attribution as
key_scope. - Secret keys and connected-app keys cannot be limited.
- Responses are cached per key limit: a limited key never receives a response cached for the whole store, and the reverse.
curl --request GET \
--url https://api.tybritelabs.com/v1/posts/{slug}/related \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.tybritelabs.com/v1/posts/{slug}/related"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.tybritelabs.com/v1/posts/{slug}/related', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.tybritelabs.com/v1/posts/{slug}/related",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "GET",
CURLOPT_HTTPHEADER => [
"Authorization: Bearer <token>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"net/http"
"io"
)
func main() {
url := "https://api.tybritelabs.com/v1/posts/{slug}/related"
req, _ := http.NewRequest("GET", url, nil)
req.Header.Add("Authorization", "Bearer <token>")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.get("https://api.tybritelabs.com/v1/posts/{slug}/related")
.header("Authorization", "Bearer <token>")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.tybritelabs.com/v1/posts/{slug}/related")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Get.new(url)
request["Authorization"] = 'Bearer <token>'
response = http.request(request)
puts response.read_body{
"anchor": {
"id": "b47080fe-d5cd-4378-b27e-b0e849320d5b",
"slug": "top-3-premium-tech-picks-for-2026",
"title": "Top 3 Premium Tech Picks for 2026"
},
"related": [
{
"id": "13676ee0-10b8-49a0-aa3f-9afcaa02a3eb",
"title": "Building the Perfect Professional Tech Ecosystem",
"slug": "building-the-perfect-professional-tech-ecosystem",
"excerpt": "Discover how the right combination of devices can transform your productivity.",
"featured_image": "https://cdn.tybritelabs.com/posts/ecosystem.jpg",
"video": null,
"published_at": "2026-01-11T12:58:50Z",
"score": 0.4839,
"reason": "Closely related subject"
}
],
"degraded": false
}
