Skip to main content
POST
/
api
/
v1
/
hr
/
attendance
/
geofence-sites
cURL
curl -sS -X POST "$FLUIDE_BASE_URL/api/v1/hr/attendance/geofence-sites" \
  -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
​
code
string
required

Stable site code referenced by mobile clients (geofenceId)

Maximum string length: 64
​
name
string
required
Maximum string length: 200
​
latitude
number
required
Required range: -90 <= x <= 90
​
longitude
number
required
Required range: -180 <= x <= 180
​
radiusMeters
number
default:150
Required range: 10 <= x <= 50000
​
requireGeofenceOnClock
boolean
default:false

Response

Create create — 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