API docs navigation
Examples
Production-style examples for common content API workflows. These examples focus on stable request patterns, including async polling where needed.
1. Deliver question content
Endpoint referenceDeliver questions
bashcurl --request POST \
--url 'https://questionstock.com/api/v1/questions' \
--header 'Authorization: Bearer qsk_v1_your_api_key' \
--header 'Content-Type: application/json' \
--data '{
"limit": 1,
"categoryIds": ["<category_id>"],
"difficulty": "mixed",
"imageRule": "optional",
"excludeQuestionIds": ["<already_served_question_id>"],
"deliveryKey": "presentation_run_001"
}'Use the same deliveryKey for the same delivery scope, presentation run, or integration batch if you want repeat avoidance to remain stable across retries and subsequent calls.
2. Probe auth and limits before launch
Endpoint referenceStatus probe
bashcurl --request GET \
--url 'https://questionstock.com/api/v1/status' \
--header 'Authorization: Bearer qsk_v1_your_api_key'Check limits.perMinute and limits.perDay at startup so your worker or backend can budget requests safely.
3. Suggest category and poll status
Endpoint referenceSubmit suggestion
bashcurl --request POST \
--url 'https://questionstock.com/api/v1/categories' \
--header 'Authorization: Bearer qsk_v1_your_api_key' \
--header 'Content-Type: application/json' \
--data '{
"name": "World Capitals",
"description": "Country-capital geography questions"
}'Poll suggestion status
bashcurl --request GET \
--url 'https://questionstock.com/api/v1/category-suggestions/<suggestion_id>' \
--header 'Authorization: Bearer qsk_v1_your_api_key'