Skip to main content
GET
Get Session Status

Authorizations

Authorization
string
header
required

Bearer token authentication using API tokens. Include the token in the Authorization header as: Authorization: Bearer <token>

Obtain tokens from your Hum representative or contact support@letshum.com. There is no self-serve API key dashboard.

Path Parameters

token
string
required

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.

Example:

"XqCmeTVgYXrbWrZFZEymkD"

Response

Session data retrieved successfully

message
string
required

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."

request_status
enum<string>
required

An informational summary returned in API response bodies: ok for successful responses, warning for standard request errors, and error for endpoint-specific failures. Integrations must use the HTTP status code, not request_status, to determine whether a request succeeded.

Available options:
ok,
warning,
error
Example:

"ok"

data
object
required

Session response data. The formatted service address and normalized address components are returned in meta.

meta
object
required

Session metadata, including normalized input values, formatted service address, session status, and the Hum data set used for the response.

qualify_status
enum<string>

The status of Internet service qualification for the address distinguishes a completed lookup from one that is not ready yet.

The answer is ready:

  • available: Providers were found and are returned in data.
  • no_service: No providers serve this address. data is []. You can act on this now, but Hum re-checks periodically, so re-validate it if you store it long term.

The answer is not ready, keep polling:

  • pending: The lookup has not finished. data is []. Retry by polling GET /sessions/{token}/services/internet.
  • retry_later: A transient upstream problem. data is []. Retry by polling GET /sessions/{token}/services/internet.

Something went wrong:

  • failed: The lookup errored for this address. data is [].

A pending lookup finishes as one of three values: available when providers are found, no_service when the lookup completes and finds none, or failed when it errors. retry_later arises separately and does not follow from pending. These three values should end the polling loop.

Available options:
available,
no_service,
pending,
failed,
retry_later
Example:

"available"