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

Talon.One Sessions API

Represents a session used for authentication purposes.Create one with the [Create session](#tag/Sessions/operation/createSession) endpoint.

Talon.One Sessions API is one of 42 APIs that Talon.One publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sessions. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and a getting-started guide.

This API exposes 2 operations across 1 path, and defines 3 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://yourbaseurl.talon.one.

2 operations 1 paths 3 schemas 1 DELETE1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://yourbaseurl.talon.one
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Talon.One Sessions API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (manager_auth). An API key is passed in the header as Authorization (management_key). By default, every request must be authenticated.

  • manager_auth — This authentication scheme relies on a bearer token that you can use to access all the endpoints of the Management API. To create the token: 1. Get a bearer to…
  • management_key — The API key authentication gives you access to the endpoints selected by the admin who created the key. Using an API key is the recommended authentication meth…

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 DELETE, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Sessions 2

Represents a session used for authentication purposes. Create one with the [Create session](tag/Sessions/operation/createSession) endpoint.

POST
/v1/sessions
Create session
createSession body → 201
DELETE
/v1/sessions
Destroy session
destroySession → 204

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Session (3 properties), EmailEntity (1 property). Each schema is shown below with its type and property counts.

Session
object
3 properties 3 required
LoginParams
EmailEntity
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

talon-one-sessions-api-openapi.yml Raw ↑

Other APIs Talon.One publishes across the network.

Talon.One Accounts and users API
Talon.One Achievements API
Talon.One Additional costs API
Talon.One Analytics API
Talon.One Applications API
Talon.One Attributes API
Talon.One Audiences API
Talon.One Braze API
Talon.One Campaign access groups API
Talon.One Campaign notifications API
Talon.One Campaign templates API
Talon.One Campaigns API
Where this information came from

This is an independent, third-party profile of Talon.One Sessions 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.