Skip to the content
Get an API key
  1. API reference
  2. Billing and usage

Get sign-in statuses

GET/public/analytics/auth-statuses
Core + Managed TransfersAuthBasicDocsSession

The sign-in requests in the range for each music service: how many sign-ins started, connected an account, or failed. Requires Client Secret authentication. Not billed.

Query parameters

startDate
stringrequired

The first day of the range (UTC), for example 2026-10-01. The day counts.

endDate
stringrequired

The last day of the range (UTC). The day counts, so startDate = endDate is one day. The range may hold at most 366 days, or 31 days for an hourly series.

integrationType
spotify | appleMusic | youtube | tidal | resso | boomplay | amazonMusic | deezer | pandora | soundCloud | youtubeMusic | napster | qobuz | qqMusic | yandexMusic | vkMusic | anghami | zvuk | gaana | jiosaavn | audiomack

Count only the requests for this music service. Leave it out for every service.

Response

200application/json · UsageAuthStatusesResponseBy service; in a service, the most frequent status first.
data
object[]
required
data[].integration_type
string
requiredThe music service.
data[].status
string
requiredinitialised: a sign-in started. success: a sign-in connected an account. error: a sign-in step failed.One of: initialised, success, error
data[].count
string
requiredSign-in requests with this status. A decimal string, so a large count stays exact.
Example answer
{
  "data": [
    {
      "integration_type": "string",
      "status": "initialised",
      "count": "string"
    }
  ]
}

Errors

400

A date is missing or not valid, endDate is before startDate, or the range is too long.

401

The request has no credentials.

403

The request does not use Client Secret authentication.

429

Your account sent more calls this minute than its rate limit allows.