Skip to main content
POST
/
api
/
v1
/
recurring
/
schedules
cURL
curl -sS -X POST "$FLUIDE_BASE_URL/api/v1/recurring/schedules" \
  -H "Authorization: Bearer $FLUIDE_ACCESS_TOKEN" \
  -H "X-Fluide-Api-Key: $FLUIDE_API_KEY" \
  -H "X-Fluide-Client-Id: fluide-developer" \
  -H "Content-Type: application/json" \
  -d '{}'
{
  "success": true,
  "message": "Operation completed successfully",
  "data": {}
}

Authorizations

​
Authorization
string
header
required

Access token JWT. Use as Authorization: Bearer . In the API playground, paste the JWT only.

​
X-Fluide-Api-Key
string
header
default:fl_dev_your_key
required

Developer API key (fl_dev_...). Required on every API call with a machine access token.

​
X-Fluide-Client-Id
string
header
default:fluide-developer
required

First-party client audience. Must match the fluide_client_id claim on the JWT. Use fluide-developer for Connect.

Body

application/json
​
templateId
string<uuid>
required
​
generateMode
enum<string>
required
Available options:
DRAFT,
AUTO_POST
​
frequency
enum<string>
required
Available options:
DAILY,
WEEKLY,
MONTHLY
​
interval
number
required
Required range: x >= 1
​
startDate
string
required

ISO date (YYYY-MM-DD)

​
dayOfMonth
number | null
Required range: 1 <= x <= 31
​
dayOfWeek
number | null

0=Sunday … 6=Saturday

Required range: 0 <= x <= 6
​
endDate
string | null
​
timezone
string
default:UTC

Response

Create recurring schedule — created

​
success
boolean
required

Whether the request succeeded

Example:

true

​
message
string
required

Human-readable outcome message (localized when i18n is configured)

Example:

"Operation completed successfully"

​
data
object

Endpoint-specific payload