Close Session
Explicitly closes an active session. While sessions automatically expire after inactivity, it’s best practice to close them when you’re done to free up resources.
Closing Behavior
- All agent processing stops immediately
- Cached results are cleared
- Session token becomes invalid
- Resources are freed
When to Close
- After completing service lookup
- When switching to a different address
- After receiving final results
- When abandoning a search
Important Notes
- Cannot be undone
- New session required for same address
- Final results should be saved before closing
- Rate limits still apply
Authorizations
Bearer token authentication using API tokens.
Include the token in the Authorization header as: Authorization: Bearer <token>
Obtain tokens through your Hum API account dashboard or contact support@letshum.com for access.
Path Parameters
The session token identifying the specific session The session token provided by the Hum API. Used to connect the response to the session in the client system.
"XqCmeTVgYXrbWrZFZEymkD"
Response
Session closed successfully
"Session closed successfully"
A status code summarizing the outcome of this response.
- ok: Request was successful
- warning: Request was processed but with some issues
- error: Request failed
ok, warning, error "ok"
Empty object for this response
Metadata about the session. Can be used to track the status of the session, time since creation, and time since last update.
