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
A JSON object that contains the service address components for the session.
The street address of the service location.
1 - 100
"29090 Tiffany Drive E"
The two-letter state abbreviation of the service location.
AL
, AK
, AZ
, AR
, CA
, CO
, CT
, DE
, FL
, GA
, HI
, ID
, IL
, IN
, IA
, KS
, KY
, LA
, ME
, MD
, MA
, MI
, MN
, MS
, MO
, MT
, NE
, NV
, NH
, NJ
, NM
, NY
, NC
, ND
, OH
, OK
, OR
, PA
, PR
, RI
, SC
, SD
, TN
, TX
, UT
, VT
, VA
, WA
, WV
, WI
, WY
"MI"
The ZIP code of the service location in 12345 or 12345-6789 format.
48034
The unit, apartment, or suite number of the service location.
1 - 50
"A2"
The city of the service location.
1 - 50
"Southfield"
A unique identifier for the campaign. This is used to track the source of the session in your internal system.
1 - 100
"1iYyMxsnTy87tFOvukTi7V"
Response
Successful session creation.
A message returned by the API. Includes a human-readable message about the status of the request.
"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
ok
, warning
, error
"ok"
Metadata about the session. Can be used to track the status of the session, time since creation, and time since last update.