Secret Key authentication
✨ Secret key authentication is available on ALL plans.
Your endpoints & projects just got more secure. You now have the option to require Secret Key authentication for your submissions. Your secret key can be found in your API key settings.
The secret key should not be exposed to your front-end and must be stored server-side. It's passed in the request via an X-Secret-Key header. You can enable this setting in your endpoint or project settings.
POST https://api.submitjson.com/v1/submit/XxXxXxXxX HTTP/1.1
content-type: application/json
X-API-Key: sjk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
X-Secret-Key: sjsk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
{
"data": {
"name": "Testing submission",
"email": "[email protected]"
}
}
REST API enhancements
We've added 10 new REST API endpoints for fetching your submissions, endpoints, and projects programmatically. These endpoints require secret key authentication, so make sure to use them server-side only.
Check out the updated REST API docs and JS Client for implementation details.
✨ The following API routes are available on all paid plans.
# Endpoints
GET /v1/endpoints
GET /v1/endpoints/:slug
GET /v1/endpoints/:slug/submissions
# Projects
GET /v1/projects
GET /v1/projects/:slug
GET /v1/projects/:slug/endpoints
GET /v1/projects/:slug/submissions
# Submissions
GET /v1/submissions
GET /v1/submissions/:id
DELETE /v1/submissions/:id
