How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Galileo Technologies auth API

The auth API from Galileo Technologies — 46 operation(s) for auth.

Galileo Technologies auth API is one of 60 APIs that Galileo Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 46 operations across 46 paths, and defines 13 schemas. It is described by OpenAPI 3.1.0, at version 1.1085.0.

Requests are made against a single base URL, https://api.galileo.ai.

46 operations 46 paths 13 schemas 15 GET31 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.1085.0
Base URL
https://api.galileo.ai
Authentication
API Key, API Key, OAuth 2.0, HTTP Basic
Resource Areas
1

Authentication & Security 4

Galileo Technologies auth API declares 4 security schemes for authenticating requests. An API key is passed in the header as Galileo-API-Key (ClassicAPIKeyHeader). An API key is passed in the header as Splunk-AO-API-Key (APIKeyHeader). It supports OAuth 2.0 (OAuth2PasswordBearer) using the password flow. It accepts HTTP basic authentication (HTTPBasic).

Paths & Operations 46

Across 46 paths, the API surfaces 46 operations — 15 GET, 31 POST. Each is listed below with its method, path, parameters, and response codes.

auth 46
POST
/login
Login Email
login_email_login_post body → 200422
POST
/login/api_key
Login Api Key
login_api_key_login_api_key_post body → 200422
POST
/login/social
Login Social
login_social_login_social_post body → 200422
GET
/saml/login
Saml Login
saml_login_saml_login_get → 200
POST
/saml/acs
Saml Acs
saml_acs_saml_acs_post → 200
GET
/saml/metadata
Saml Metadata
saml_metadata_saml_metadata_get → 200
POST
/logout
Logout
logout_logout_post → 200
POST
/verify_email
Verify Email
verify_email_verify_email_post 1 param body → 200422
GET
/tokendeprecated
Get Token
get_token_token_get 2 params → 200422
POST
/refresh_token
Refresh Token
refresh_token_refresh_token_post 1 param → 200422
GET
/v1/token
Get Token
get_token_v1_token_get 2 params → 200422
POST
/v1/login
Login Email
login_email_v1_login_post body → 200422
POST
/v1/login/api_key
Login Api Key
login_api_key_v1_login_api_key_post body → 200422
POST
/v1/login/social
Login Social
login_social_v1_login_social_post body → 200422
GET
/v1/saml/login
Saml Login
saml_login_v1_saml_login_get → 200
POST
/v1/saml/acs
Saml Acs
saml_acs_v1_saml_acs_post → 200
GET
/v1/saml/metadata
Saml Metadata
saml_metadata_v1_saml_metadata_get → 200
POST
/v1/verify_email
Verify Email
verify_email_v1_verify_email_post 1 param body → 200422
POST
/v1/refresh_token
Refresh Token
refresh_token_v1_refresh_token_post 1 param → 200422
GET
/v2/token
Get Token
get_token_v2_token_get 2 params → 200422
POST
/v2/login
Login Email
login_email_v2_login_post body → 200422
POST
/v2/login/api_key
Login Api Key
login_api_key_v2_login_api_key_post body → 200422
POST
/v2/login/social
Login Social
login_social_v2_login_social_post body → 200422
GET
/v2/saml/login
Saml Login
saml_login_v2_saml_login_get → 200
POST
/v2/saml/acs
Saml Acs
saml_acs_v2_saml_acs_post → 200
GET
/v2/saml/metadata
Saml Metadata
saml_metadata_v2_saml_metadata_get → 200
POST
/v2/verify_email
Verify Email
verify_email_v2_verify_email_post 1 param body → 200422
POST
/v2/refresh_token
Refresh Token
refresh_token_v2_refresh_token_post 1 param → 200422
GET
/public/v1/token
Get Token
get_token_public_v1_token_get 2 params → 200422
POST
/public/v1/login
Login Email
login_email_public_v1_login_post body → 200422
POST
/public/v1/login/api_key
Login Api Key
login_api_key_public_v1_login_api_key_post body → 200422
POST
/public/v1/login/social
Login Social
login_social_public_v1_login_social_post body → 200422
GET
/public/v1/saml/login
Saml Login
saml_login_public_v1_saml_login_get → 200
POST
/public/v1/saml/acs
Saml Acs
saml_acs_public_v1_saml_acs_post → 200
GET
/public/v1/saml/metadata
Saml Metadata
saml_metadata_public_v1_saml_metadata_get → 200
POST
/public/v1/verify_email
Verify Email
verify_email_public_v1_verify_email_post 1 param body → 200422
POST
/public/v1/refresh_token
Refresh Token
refresh_token_public_v1_refresh_token_post 1 param → 200422
GET
/public/v2/token
Get Token
get_token_public_v2_token_get 2 params → 200422
POST
/public/v2/login
Login Email
login_email_public_v2_login_post body → 200422
POST
/public/v2/login/api_key
Login Api Key
login_api_key_public_v2_login_api_key_post body → 200422
POST
/public/v2/login/social
Login Social
login_social_public_v2_login_social_post body → 200422
GET
/public/v2/saml/login
Saml Login
saml_login_public_v2_saml_login_get → 200
POST
/public/v2/saml/acs
Saml Acs
saml_acs_public_v2_saml_acs_post → 200
GET
/public/v2/saml/metadata
Saml Metadata
saml_metadata_public_v2_saml_metadata_get → 200
POST
/public/v2/verify_email
Verify Email
verify_email_public_v2_verify_email_post 1 param body → 200422
POST
/public/v2/refresh_token
Refresh Token
refresh_token_public_v2_refresh_token_post 1 param → 200422

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are Body_login_email_public_v2_login_post (6 properties), Body_login_email_v2_login_post (6 properties), Body_login_email_v1_login_post (6 properties), Body_login_email_public_v1_login_post (6 properties). Each schema is shown below with its type and property counts.

Body_login_email_v1_login_post
object
6 properties 2 required
SocialProvider
string
EmailVerificationRequest
object
1 property 1 required
GetTokenResponse
object
3 properties 2 required
ApiKeyLoginRequest
object
1 property 1 required
Body_login_email_public_v1_login_post
object
6 properties 2 required
Body_login_email_login_post
object
6 properties 2 required
ValidationError
object
5 properties 3 required
Token
object
2 properties 1 required
Body_login_email_v2_login_post
object
6 properties 2 required
Body_login_email_public_v2_login_post
object
6 properties 2 required
SocialLoginRequest
object
3 properties 1 required
HTTPValidationError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

galileo-technologies-auth-api-openapi.yml Raw ↑

Other APIs Galileo Technologies publishes across the network.

Galileo Technologies annotation API
Galileo Technologies annotation_queue API
Galileo Technologies annotation_queue_records API
Galileo Technologies api_keys API
Galileo Technologies assistant API
Galileo Technologies Audit Logs API
Galileo Technologies auto-metric-suggestions API
Galileo Technologies code-metric-generation API
Galileo Technologies component_views API
Galileo Technologies custom_dashboards API
Galileo Technologies data API
Galileo Technologies dataset API
Where this information came from

This is an independent, third-party profile of Galileo Technologies auth API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.