API reference › Broadcast and dispatch › Priority based broadcasts
Retrieve a priority based broadcast by ID
GET /v1/priority-based-broadcasts/{priority_based_broadcast}
- Scope
settings_broadcast_dispatch:read- Roles
- admin, scheduler
Fetch an priority based broadcast by its ID.
Parameters
Path parameters
| Name | Type | Description |
|---|---|---|
priority_based_broadcast required | integer | ID of priority based broadcast to retrieve. Example |
Every call also sends Authorization and X-Tenant-ID; see Getting started.
Example request
curl "https://api.fetchfido.ai/v1/priority-based-broadcasts/{priority_based_broadcast}" \
-H "Authorization: Bearer $FIDO_API_KEY" \
-H "X-Tenant-ID: $FIDO_TENANT_ID"Try it
Responses
200 Priority based broadcast retrieved successfully
Priority based broadcast retrieved successfully.
{
"success": true,
"message": "Priority based broadcast retrieved successfully!",
"data": {
"id": 1,
"priority": "string",
"initialPoolSize": 1,
"cycleInterval": 1,
"cycleIntervalUnit": "minutes",
"maximumBroadcastRounds": 1,
"escalationTimeout": 1,
"escalationTimeoutUnit": "string"
}
}Response fields (11)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
data | object | |
data.id | integer | Example |
data.priority | string | Example |
data.initialPoolSize | integer | Example |
data.cycleInterval | integer | Example |
data.cycleIntervalUnit | string | Example |
data.maximumBroadcastRounds | integer | Example |
data.escalationTimeout | integer | Example |
data.escalationTimeoutUnit | string | Example |
401 Not signed in
Missing, invalid or expired API key.
{
"success": false,
"message": "Invalid API key. Org and user tier keys must send an X-Tenant-ID header naming the organization the key was issued for.",
"errors": null,
"code": "API_KEY_MISSING"
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | Null on this status. |
code | string | Machine-readable reason, for branching on in client code. One of: |
403 Not allowed
Scope, tenant, IP allow-list or RBAC check failed.
{
"success": false,
"message": "You don't have permission to access this endpoint. This API key is missing the 'settings_broadcast_dispatch:read' scope.",
"errors": null,
"code": ""
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | Null on this status. |
code | string | Always empty on this status. Example |
404 Not found
Priority based broadcast not found.
{
"success": false,
"message": "Priority based broadcast with ID 10 not found."
}Response fields (2)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
429 Too many requests
Rate limit exceeded. See Retry-After.
{
"success": false,
"message": "You've exceeded this API key's rate limit of 120 requests per minute. Try again in 37 seconds.",
"errors": null,
"code": "RATE_LIMITED"
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | Null on this status. |
code | string | Machine-readable reason, for branching on in client code. One of: |
500 Server error
Internal server error.
{
"success": false,
"message": "Something went wrong!"
}Response fields (2)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |