Sessions
Get Session Status
Retrieves the current status of a session, including normalized address data and processing status of various Hum AI agents.
Polling Guidelines
- Initial request: Immediately after session creation
- Subsequent requests: Every 2-3 seconds until agents complete
- Maximum polling duration: 30 seconds
- Implement exponential backoff if status doesn’t change
Status Codes
- 200: Session active and data available
- 202: Session active but still processing
- 410: Session expired or closed
Response Data
- Normalized address
- Geocoding results
- Agent processing status
- Available services (when ready)
Important Notes
- The session token is part of the URL path for all requests after creation
- The session token is required for all subsequent requests
- The session token is valid for 30 minutes of inactivity
- Rate limits apply to all requests
Example Response
{
"message": "Session data retrieved successfully",
"request_status": "ok",
"data": {
"service_address": {
"normalized": "29090 TIFFANY DR E, SOUTHFIELD, MI 48034",
"latitude": 42.501721,
"longitude": -83.286263
}
},
"meta": {
"agent_status": {
"geocoding": "matched",
"internet": "pending"
}
}
}
GET
Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Path Parameters
The session token identifying the specific session
Example:
"Xxjljd2CQgobOvPR3X6Lat"
Response
200
application/json
Session data retrieved successfully
A message returned by the API. Includes a human-readable message about the status of the request.
Example:
"What happened in the most recent request."
A status code summarizing the outcome of this response.
- ok: Request was successful
- warning: Request was processed but with some issues
- error: Request failed
Available options:
ok
, warning
, error
Example:
"ok"
Metadata about the session. Can be used to track the status of the session, time since creation, and time since last update.
Was this page helpful?