curl --request DELETE \
--url https://api.gigstack.io/v2/users/me/notifications/{notificationId} \
--header 'Authorization: Bearer <token>'const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/users/me/notifications/{notificationId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/users/me/notifications/{notificationId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text){
"success": true,
"data": {
"id": "<string>",
"notification_id": "<string>",
"team_id": "<string>",
"delivered_at": 123,
"read_at": 123,
"dismissed_at": 123,
"type": "<string>",
"priority": "<string>",
"title": "<string>",
"body": "<string>",
"cta": {
"text": "<string>",
"link": "<string>"
},
"expires_at": 123
},
"timestamp": 123
}Dismiss a notification
Requires a verified Firebase ID token or signed, active personal MCP token. Team API keys and OAuth client credentials cannot act as their creator. Firebase callers may access their own identity before joining a team. MCP callers remain subject to current credential/team authorization. Authentication is verified in the backend, including when requests pass through the API gateway.
curl --request DELETE \
--url https://api.gigstack.io/v2/users/me/notifications/{notificationId} \
--header 'Authorization: Bearer <token>'const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/users/me/notifications/{notificationId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/users/me/notifications/{notificationId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text){
"success": true,
"data": {
"id": "<string>",
"notification_id": "<string>",
"team_id": "<string>",
"delivered_at": 123,
"read_at": 123,
"dismissed_at": 123,
"type": "<string>",
"priority": "<string>",
"title": "<string>",
"body": "<string>",
"cta": {
"text": "<string>",
"link": "<string>"
},
"expires_at": 123
},
"timestamp": 123
}Authorizations
Authentication Method: HTTP Bearer token.
The runtime requires the literal Bearer prefix — a bare token in the
Authorization header is rejected with 401 unauthorized.
Header Format: Authorization: Bearer YOUR_API_KEY
Your API key is a JWT. Live keys operate on live data (livemode: true);
test keys operate on isolated test data (livemode: false).
Get your key at: app.gigstack.pro/settings?tab=api
Errors: credential failures are answered by the authentication layer with a raw
{ "message": … } body, not the standardized envelope — 401 for a missing, malformed or
expired token, 403 for a revoked key or a plan without API access. See the Unauthorized
and AuthForbidden responses.
Path Parameters
Recipient record ID from data[].id.
^[A-Za-z0-9_-]{1,256}$