Sessions
Create New Session
Creates a new session for processing a service address. This is typically the first endpoint called when starting a new address lookup flow.
Request Flow
- Submit service address components
- Receive a session token
- Use session token in the URL path for subsequent requests
Processing
Upon session creation, Hum AI agents begin:
- Validating and normalizing the address
- Geocoding the location
- Identifying available service providers
- Gathering plan and pricing information
Response Handling
- 201: Session created successfully, proceed with GET requests to monitor status
- 422: Invalid address components, check error details
- 429: Rate limit exceeded, implement exponential backoff
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 Usage
POST /sessions
{
"street1": "29090 Tiffany Drive E",
"city": "Southfield",
"state": "MI",
"zip": "48034"
}
POST
Authorizations
Bearer token authentication using JWT 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.
Body
application/json
A JSON object that contains the service address components for the session.
The body is of type object
.
Response
201
application/json
Successful session creation.
The response is of type object
.