Error codes

Every code the player, the loader and the control plane can report. Codes are permanent: one is never reused or renumbered, so a search for it years from now still lands here.

info
Logged for diagnostics. The viewer sees nothing.
degraded
Something degraded. Playback continues, a feature may be missing.
unplayable
This media cannot play, but the player is alive and can be given new media.
rejected
A control-plane request was refused. Never reachable from a player (C3).

Setup and configurationPBP-100000 – PBP-100999

  • PBP-100001rejected

    This deployment has no object storage configured, so it cannot accept uploads.

    Registering media by URL is unaffected, and so is every media item already registered. A deployment that configures no object storage is a working deployment with one fewer way to add media, not a broken one.

Loader, manifest and version resolutionPBP-101000 – PBP-101999

  • PBP-101001degraded

    Version manifest could not be fetched. Falling back to the last cached manifest.

    Cached manifest → last known-good pinned set → baked-in fallback version.

  • PBP-101002degraded

    Version manifest did not match the expected schema. Falling back.

    Treated as unreachable. Never parsed partially.

  • PBP-101003degraded

    Version manifest declares a protocol version this loader does not support.

    Falls back to the baked-in version, which always speaks a protocol it knows.

  • PBP-101004degraded

    Artefact content hash did not match the value in the manifest.

    Fails closed to the fallback version. The tampered artefact is never executed.

  • PBP-101005degraded

    No compatible artefact set could be resolved for this property.

    Server returns the last known-good satisfiable set and raises an alert (§4.6).

  • PBP-101006degraded

    The element named by data-target does not exist.

    The loader creates a container after its own script tag and mounts there, so the page still gets a player.

  • The version this property resolves to has been withdrawn. A replacement was served.

    The manifest service serves the next precedence down instead (§4.4), and resolvedBy ends ;withdrawn:<version> so the page can see why its version changed. Logged by the manifest service; the player plays the substitute as it would any release (§4.7).

Licence and entitlementPBP-102000 – PBP-102999

  • PBP-102001degraded

    No licence key was supplied. Running in unlicensed mode.

    Unlicensed mode. Video plays; configuration is stripped and the API is gated.

  • PBP-102002degraded

    Licence key was not recognised. Running in unlicensed mode.

    Unlicensed mode.

  • PBP-102003degraded

    Licence key has been revoked. Running in unlicensed mode.

    Unlicensed mode.

  • PBP-102004degraded

    This origin is not on the property’s allowed-origin list. Running in unlicensed mode.

    Unlicensed mode. Never a blocked page, and never an HTTP error (§5.5).

  • PBP-102005degraded

    Account is past due. A grace period is in effect.

    Notice → grace → unlicensed. Playback is unaffected throughout.

  • This method is unavailable in unlicensed mode.

    The call does nothing and a warning names the method and the reason (§5.6 lever 3). Playback through the player’s own controls is unaffected.

  • PBP-102007degraded

    This key was issued for another platform. Running in unlicensed mode.

    Unlicensed mode. Keys are issued per platform, so a leaked device key never licenses the web property (§5.1).

  • PBP-102008degraded

    This app’s bundle identifier is not on the key’s list. Running in unlicensed mode.

    Unlicensed mode, the device counterpart of an origin mismatch (§5.5).

  • PBP-102009degraded

    The activation request could not be read, which means an SDK bug. Running in unlicensed mode.

    Unlicensed mode. The service answered 200 with an unlicensed token, as it answers everything.

  • PBP-102010degraded

    The licence token did not verify. Running in unlicensed mode.

    Unlicensed mode. A token that fails any check is never partly trusted.

  • PBP-102011degraded

    Activation could not be reached. Using the cached licence.

    The cached licence applies until its grace period ends, then unlicensed mode. Playback never waits for activation.

  • PBP-102012degraded

    A development key cannot license a release build. Running in unlicensed mode.

    Unlicensed mode. A development key licenses debuggable builds and simulators only (§5.1).

  • This SDK version is deprecated. Support ends on the date logged with this warning.

    Nothing changes. A developer reads it in the log, with the end-of-support date; a viewer never sees it.

  • PBP-102014degraded

    This SDK version has been told to run its safe subset. Update to a supported release.

    The SDK runs its safe subset: no optional modules and stock controls. Licensed playback and the API are unaffected (§4.8).

  • PBP-102030degraded

    Offline download needs a licensed key on the Business edition or above. Streaming the item instead.

    No copy is made, or the one kept does not play; the item streams from its own sources as before. A lapsed feature withdraws the copy, never playback (C3).

  • PBP-102031degraded

    The licence this offline copy plays under has passed its grace. Streaming the item instead.

    The offline copy does not play, and the item streams from its own sources instead, under whatever licence the device holds. The copy plays again as soon as a fresh token arrives (licence-protocol, Offline download).

  • PBP-102050degraded

    This app is not signed with a certificate the key names. Running in unlicensed mode.

    Unlicensed mode: the app plays, watermarked, with the API gated (§5.5). A production Android key that names signing certificates licenses only an app signed with one of them.

  • PBP-102053degraded

    Activation withdrew this key’s offline copies. They were deleted.

    Every offline copy made under the key is deleted. Streaming is unaffected, and plays as the new licence says. Only an answer from activation withdraws a copy — never a network failure, the store, or a token that did not verify (licence-protocol, Offline download).

Playback engine and mediaPBP-103000 – PBP-103999

  • PBP-103001unplayable

    No playback engine could play any source for this media.

    Every source was offered to every engine that declared its type and each declined. The player stays alive and can be given new media: it shows an error state with retry, never a blank frame (§L1).

  • No engine on this platform answered probably or maybe for this source.

    The source is skipped before a byte is fetched and the next one is offered. Only when every source is declined does PBP-103001 follow.

  • PBP-103003unplayable

    The playback engine reported a media error.

    Error state with retry. Retry re-runs source selection from the top, so a transient decoder fault does not retire a source for good.

  • PBP-103004degraded

    The browser refused to start playback without a user gesture.

    Retried muted; if that is refused too, the player shows its play control and waits. A browser policy is not an error the page can act on.

  • PBP-103005unplayable

    The DRM licence request for this source failed.

    No longer emitted: PBP-107021 and PBP-107022 say which way the request failed.

  • PBP-103006degraded

    The browser could not play this media’s sound on the audio output device.

    Muted, and resumed from the same position, once per item: the picture plays on and the viewer can unmute once their device works again. A second failure on the same item, or one while already muted, is PBP-103003.

Network and deliveryPBP-104000 – PBP-104999

  • PBP-104001unplayable

    The media manifest (HLS or DASH) could not be fetched.

    The source is retired and the next source is offered to the engines. With none left, PBP-103001.

  • PBP-104002degraded

    A media segment failed to download.

    The engine retries with backoff and the player shows buffering. Reported once per stall, not once per segment.

  • PBP-104003unplayable

    The playlist feed could not be fetched.

    The player shows its empty state with a retry and stays alive. Nothing named by the page can be played, and it says so.

  • PBP-104004degraded

    The player configuration document could not be fetched. Using defaults.

    The player runs on defaults. A configuration that cannot be fetched is a player with fewer opinions, not a blank frame (C3).

  • PBP-104005unplayable

    This media is unavailable: the account that hosts it is suspended.

    The media host refuses every file of a suspended account, signed links issued before the suspension included, with 403 and this code in X-PBP-Error. The item cannot play; the page and the player stay alive and can be given other media (C3). It plays again once the account is unsuspended, within a minute.

  • PBP-104006unplayable

    This video is unavailable: its account has used its free delivery allowance.

    The item shows its error state with this message and the player stays alive; other items, and media hosted elsewhere, still play. The free-tier account that hosts it is past several times its delivery or encode allowance with no card on file, so no new signed media URLs are issued until a card is added or the next period begins. URLs already handed out keep working until they expire. Never applied to a paid plan.

  • PBP-104007unplayable

    This media is unavailable through a proxy: the account that hosts it delivers to viewers directly.

    The media host refuses a request that came through a proxy, a CDN or a datacenter network for an account an operator set to deliver to viewers directly (Docs/plans/delivery-integrity.md §4.4), with 403 and this code in X-PBP-Error. A viewer on their own connection still plays; the page and the player stay alive (C3). Never a default: an operator sets it per account.

PluginPBP-105000 – PBP-105999

  • PBP-105001degraded

    A plugin could not be loaded or registered.

    Playback continues without that feature (§18.3.3). A plugin that fails to fetch, or throws while registering, is logged and forgotten.

  • PBP-105002degraded

    Plugin content hash did not match the value in the manifest.

    The plugin is never executed and playback continues without it. A tampered artefact is refused, not retried.

  • PBP-105003degraded

    A locale could not be loaded; the controls are in English.

    The controls stay in English, left to right, and playback is untouched (C3). Not retried for that player.

TelemetryPBP-106000 – PBP-106999

  • The telemetry buffer overflowed and events were dropped.

    The oldest buffered events are discarded and playback is untouched (§18.3.4). Reported once per overflow.

DRM and content protectionPBP-107000 – PBP-107999

  • PBP-107001unplayable

    The key for this encrypted stream was refused.

    Renewed like a refused signed URL. Refused again, the error state with retry: no frame is ever shown undecrypted.

  • PBP-107020unplayable

    No key system on this platform matches this media’s protection.

    The source is declined before a byte is fetched and the next is offered; with none left, error state with retry, player alive.

  • PBP-107021unplayable

    The licence server refused the licence request.

    The source is retired and the next is tried; with none left, error state with retry, player alive. Never retried on its own: the server is the customer’s (§6.1).

  • PBP-107022unplayable

    The licence server could not be reached.

    As PBP-107021. A CORS refusal and ten seconds without an answer both read as unreachable.

  • PBP-107023unplayable

    The FairPlay certificate could not be fetched.

    As PBP-107021.

  • This item is protected, and protected media cannot be downloaded for offline play yet.

    No copy is made. The item streams, protected, exactly as before; keeping a protected copy needs persistent keys from the customer’s licence server, which pass-through does not yet ask for.

Identity and sessionPBP-109000 – PBP-109999

  • PBP-109001rejected

    Email or password was not recognised.

    No session is issued. The same code answers an unknown email and a wrong password, so the response cannot be used to enumerate accounts.

  • PBP-109002rejected

    No session token was supplied.

    The request is refused. Routes are protected unless marked @Public, so the failure mode of forgetting is a locked door.

  • PBP-109003rejected

    This session has ended. Sign in again.

    The request is refused. A signature that still verifies is not enough — the session record is the authority, which is what makes sign-out immediate rather than a wait for the token to expire.

  • PBP-109004rejected

    An account already exists for this email address.

    No account, user or credential is created. Nothing about the existing account is disclosed — though the answer itself says the address is taken, which is why registration stops giving it once it confirms addresses by email (REGISTRATION_CONFIRMS_EMAIL).

  • PBP-109005rejected

    Refresh token was rejected. Sign in again.

    The session ends. The dashboard returns to sign-in rather than retrying, since a refresh token is single-use and a rejected one never becomes valid again.

  • PBP-109006rejected

    The credential provider could not be reached. Try again shortly.

    Sign-in, registration and password changes are refused while the credential provider is down. Sessions already issued keep working: they are verified against Redis and a cached key set, neither of which needs the provider. Signing out everywhere still ends every session record, and answers this because the refresh tokens could not be revoked with them.

  • PBP-109007rejected

    This user is suspended. Contact the account owner.

    No session is issued and any live session is revoked at its next request. Playback for the account is unaffected: suspending an operator is not a licence action (§5.5).

  • PBP-109008rejected

    No such property.

    The request is refused as not found. A property belonging to another account and a property that does not exist get the same answer, so the id space cannot be used as an oracle for which properties exist.

  • PBP-109009rejected

    No such media.

    The request is refused as not found. Media belonging to another property and media that does not exist get the same answer, for the same reason PBP-109008 gives one.

  • PBP-109010rejected

    That confirmation link has expired or was already used. Sign in, or register again.

    No session is issued. The link was not one the credential provider issued, has expired, or was used already; signing in, or registering again, sends a new one.

  • PBP-109011rejected

    Confirm your email address first — the link is in your inbox.

    No session is issued. The password was right and the address has not been confirmed yet; the link in the confirmation email finishes it. Only reachable with the right password, so it tells nobody else anything.

  • PBP-109012rejected

    Password reset is not set up on this deployment yet.

    No email is sent, and the answer is the same for every address. The deployment has no DASHBOARD_URL, so a reset link would have nowhere to land; setting it switches reset on. Sessions already issued are unaffected.

  • PBP-109014rejected

    Only an owner of this account can do that.

    Nothing changes and the session is untouched — a refusal, not a sign-out. Members read everything an owner can; changing people, invitations and licence keys is an owner’s.

  • PBP-109015rejected

    That address already has a PB Play account. One person belongs to one account, for now.

    No invitation is recorded and no email is sent, and nobody joins. A person belongs to one account for now (hardening §10, decision 13), so an address with a user in any account cannot be invited — nor one the credential provider already holds a confirmed credential for that no invitation of ours made.

  • PBP-109016rejected

    Invitations are not set up on this deployment yet.

    No invitation is recorded and no email is sent. The deployment has no DASHBOARD_URL, so the link would have nowhere to land; setting it, with the credential provider’s mailer and ${DASHBOARD_URL}/invite/accept on its redirect allowlist, switches invitations on. Everyone already in the account is unaffected.

  • PBP-109017rejected

    Owners of a team need a second factor.

    Nothing changes. An owner of an account with more than one person holds a second factor: it is needed to invite anyone, to be made an owner of a team and to act as one, and it cannot be turned off while the team exists. An owner without one — invited as an owner, or back in with a recovery code — is refused every owner action until it is on again. Turning it on under Security is the way through.

  • PBP-109018rejected

    That invitation has expired, was withdrawn, or was already used. Ask the owner to send a new one.

    No user is created and no session is issued. The link was not one the credential provider issued, or the invitation behind it has passed its seven days, was revoked, or was accepted already; the owner sending it again makes a new one.

  • PBP-109019rejected

    An account needs an owner. Make someone else an owner first.

    Nothing changes. The last owner of an account can be neither removed nor made a member, so no account is ever left without someone who can manage its people and keys.

  • PBP-109020rejected

    No such member.

    The request is refused as not found. A person in another account and a person who does not exist get the same answer, for the reason PBP-109008 gives one.

  • PBP-109021rejected

    No such invitation.

    The request is refused as not found. An invitation from another account, one already accepted or revoked, and one that never existed get the same answer.

  • PBP-109022rejected

    This account uses a second factor. Sign in again.

    No session is issued, and the credential provider’s session behind the token is ended. A user with a second factor on is only ever given a session the factor proved (aal2): a password alone, a refresh of a session that never passed it, or an emailed link signs nobody in. Signing in asks for the code.

  • PBP-109023rejected

    That code was not right. Try the one your app shows now.

    Nothing changes and no session is issued. The code — from the authenticator app, or one of the recovery codes — can be tried again; a sign-in allows five tries before it starts over from the password.

  • PBP-109024rejected

    That sign-in took too long. Enter your password again.

    No session is issued. The step between a password and its code lasts five minutes and ends at the first session it makes or the fifth wrong code; after that, sign-in starts again from the password.

  • PBP-109025rejected

    A second factor is already on. Turn it off first to set up another.

    Nothing changes. One authenticator per person: replacing it is turning it off with a current code and setting a new one up.

  • PBP-109026rejected

    No second factor is on.

    Nothing changes. New recovery codes and turning the factor off both need one to be on.

  • PBP-109040rejected

    That is not an API token.

    The request is refused before anything is looked up. An API token is pbp_tok_ and thirty-two base-32 characters; anything else that starts that way was truncated or mistyped.

  • PBP-109041rejected

    That API token was not recognised.

    The request is refused. The token is well formed and was never issued — only its digest is stored, so a token lost is a token replaced, never recovered.

  • PBP-109042rejected

    This API token was revoked.

    The request is refused and nothing changes. An owner revoked the token, which takes effect on the next request.

  • PBP-109043rejected

    This API token has expired.

    The request is refused and nothing changes. The token reached the expiry it was issued with; an owner issues a new one.

  • PBP-109044rejected

    An API token cannot do that. Sign in to the dashboard instead.

    The request is refused and nothing changes. An API token acts for an account, never as a person: it cannot sign in, reset a password, change a second factor, manage people or issue another token. Those need a signed-in owner.

  • PBP-109050rejected

    Single sign-on is not set up for that address.

    Nothing starts. No Business account has verified that domain and registered a provider. Passwords are unaffected.

  • PBP-109051rejected

    Single sign-on could not be completed. Start again from the sign-in page.

    No session, and the sign-in page says so: no code, a used or expired one, another browser, or an identity provider error. Start again.

  • PBP-109052rejected

    Your identity provider signed in an address outside this account’s verified domains.

    No session. An identity provider is believed only about its own account’s verified domains.

  • PBP-109053rejected

    That address belongs to another PB Play account, so single sign-on cannot sign it in here.

    No session, and nothing moves. SSO never signs in a person another account holds; that account removes them first.

  • PBP-109054rejected

    This account does not add people through single sign-on. Ask an owner to invite you.

    No session, and nobody is added. The account does not add people through SSO; an owner invites them.

  • PBP-109055rejected

    Your organisation signs in with single sign-on. Choose “Sign in with SSO”.

    No session, and the provider session is ended. Where SSO is required a password signs nobody in — except an owner with a second factor, the break-glass.

  • PBP-109056rejected

    Single sign-on for this account has changed. Sign in again.

    No session. Its identity provider is no longer the account’s, so it is not renewed.

  • PBP-109057rejected

    Set up a second factor after signing in with your password. With single sign-on, your identity provider’s is used.

    Nothing changes. On an SSO sign-in the identity provider’s MFA stands in for ours; a factor is set up after a password sign-in.

  • PBP-109058rejected

    Single sign-on is not available on this deployment yet.

    Nothing starts. SAML is off at the credential provider, or DASHBOARD_URL is unset (Docs/runbooks/single-sign-on.md). Passwords are unaffected.

  • PBP-109070rejected

    Your role in this account does not allow that.

    Nothing changes and the session is untouched — a refusal, not a sign-out. The role this session holds in the account, its property role, or its API token scope does not reach this action; owner, admin, member and billing each reach a fixed set of routes.

  • PBP-109071rejected

    This account is suspended. Contact PB Play support.

    Every dashboard and API route of the account is refused, every session in it was ended when it was suspended, and no one can sign in to it or switch into it. Its licence keys resolve unlicensed and its hosted media stops being delivered (PBP-104005); the customer’s page still loads (C3). An operator unsuspends it.

  • PBP-109072rejected

    You are not a member of that account.

    No session is issued, or the session stays in the account it was in. The person holds no membership of the account named — or, at sign-in, of any account at all; an owner or admin of the account can invite them.

  • PBP-109073rejected

    A PB Play support session can only read.

    Nothing changes. A PB Play support session reads the account as its owner would, and may change nothing: every request but a read is refused, on every route. Each page it reads is recorded in the account’s audit log.

  • PBP-109074rejected

    This support link has expired. Ask PB Play support for a new one.

    No session is issued. A support link carries a one-time code that lasts sixty seconds and works once; this one was used, expired or never issued. PB Play support opens a new one.

  • PBP-109075rejected

    That address cannot receive email. Check it and try again.

    No invitation is recorded and no email is sent. The credential provider refused the address as one no mail can reach — a reserved domain such as .test, or a malformed address — so the invitation could never arrive.

Control plane resourcesPBP-110000 – PBP-110999

  • PBP-110001rejected

    No such georestriction rule.

    The request is refused as not found. Media pointing at the rule is untouched.

  • PBP-110002rejected

    No such playlist.

    The request is refused as not found. On the public feed the same code is carried, and the embedding page renders an empty player rather than an error.

  • PBP-110003rejected

    No such player.

    The request is refused as not found. A page embedding a removed player still plays: the public route answers the same way, and an embed with no player configuration falls back to defaults rather than failing (C3).

  • PBP-110004rejected

    No such ad schedule.

    The request is refused as not found. A schedule belonging to another property and one that does not exist get the same answer, for the reason PBP-109008 gives.

  • PBP-110005rejected

    That ad schedule belongs to another property.

    The player is not saved. A schedule may only be named by players in the property that owns it, and a reference that crossed properties would leak both the schedule and the fact that it exists.

  • PBP-110006rejected

    That playlist belongs to another property.

    The player is not saved. A playlist may only be named as related content by players in the property that owns it, and a reference that crossed properties would show one customer’s catalogue on another’s page.

  • PBP-110007rejected

    This record changed after you opened it.

    The write is refused and nothing is stored. A record here is saved whole, so a write built from a copy taken before somebody else changed it would put every stale field back — and the pipeline is one of those writers, so the loser is often a measured duration or a finished rendition rather than another person’s typing. The caller re-reads and decides; only a caller that sent what it believed the record to be can be told.

  • PBP-110008rejected

    That georestriction rule belongs to another property.

    The media is not saved. A georestriction rule may only be applied by media in the property that owns it: enforced, a reference that crossed properties would serve one customer’s content under another customer’s rights policy.

  • PBP-110009rejected

    That option is not included in this account’s edition.

    The player is not saved. An option gated above the account’s edition may keep the value it already has and may always go back to its default, but may not be set to anything else. The message names the option and the edition it needs; a licensed player on this account would reset it to its default in any case.

  • PBP-110010rejected

    This upload would take the property past its storage allowance.

    The upload is not started. The property would keep more in storage than its account’s edition includes; the message says how much is used and how much is allowed. Removing media frees storage at once. Nothing already stored is touched, and nothing stops playing.

  • PBP-110011rejected

    That Idempotency-Key was already used for a different request.

    Nothing is done. The Idempotency-Key was already used for a request with a different body, or is not a key at all (empty, or longer than 255 characters). A key names one request; reusing it for another is a bug in the caller, and guessing which request was meant would be worse.

  • PBP-110012rejected

    A request with that Idempotency-Key is still being handled. Retry shortly.

    Nothing is done. A request carrying the same Idempotency-Key is still being handled; retrying shortly returns its answer. Running it twice is the thing the key exists to prevent.

  • PBP-110013rejected

    The audit log is included from the Business edition.

    The audit log is not returned. It is recorded for every account and readable from the Business edition (§7.1), so an account that moves up finds its history already there.

  • PBP-110014rejected

    Production keys are included from the Starter edition.

    No key is issued. Development keys stay free on every edition (§5.1).

  • PBP-110015rejected

    No such key.

    Nothing changes.

  • PBP-110016rejected

    No such app.

    Nothing is returned. The app does not exist, or was removed; an app id from another property reads the same way.

  • PBP-110017rejected

    That player belongs to another property.

    The app is not saved. An app may only play with a player from the property that owns it; a reference that crossed properties would show one customer’s configuration inside another’s app.

  • PBP-110018rejected

    Too many requests. Try again shortly.

    The request is refused before it reaches a handler, and nothing is changed. The allowance is per address per minute — the public surface’s for the public routes, the auth routes’ for signing in — and counted in Redis, so every instance of a service shares it; the message says when to try again. A player on a customer’s page never sees this in normal use: its reads are cached, and a feed or player document it cannot fetch is an empty player, not an error (C3).

  • PBP-110019rejected

    Bundle identifiers belong to Android and iOS keys, not web keys.

    Nothing is saved. A web key is limited by origin, and a device key by the apps it names (licence-protocol, Keys).

  • PBP-110020rejected

    Version pinning and beta access are included from the Growth edition.

    Nothing changes: the property keeps following its channel. Pinning a version and following beta are included from the Growth edition (§7.2); following stable is included on every edition.

  • PBP-110021rejected

    That version is not a published release, or it has been withdrawn.

    Nothing changes. A pin must name a published release that is not withdrawn; the Versions screen lists them.

  • PBP-110022rejected

    Real-time analytics and reports are included from the Growth edition.

    Nothing is shown. Real-time analytics, reports and export are included from the Growth edition (§7.2); the overview is on every edition, over the window its edition keeps. Collection is never gated: every edition is measured.

  • PBP-110023rejected

    That channel does not exist.

    Nothing changes. A property may follow dev, beta, stable, or a long-term support line that has been published; the Versions screen lists them.

  • PBP-110024rejected

    Long-term support channels are included from the Business edition.

    Nothing changes. A long-term support line (§4.3 lts-N) is included from the Business edition (§7.2); below it a property follows stable, beta or a pin.

  • PBP-110025rejected

    This deployment already holds as many properties as its licence allows.

    No property is created. A self-hosted deployment holds as many properties as its deployment licence allows (licence-protocol, Self-hosted deployments); the existing ones keep working. A renewed licence with a higher limit lifts it.

  • PBP-110030rejected

    No such collection.

    The request is refused as not found, and nothing is changed. A bulk action naming a collection that is not this property’s changes no item at all. Nothing a player reads names a collection, so no page ever sees this; a dynamic playlist ruled by a deleted collection resolves to an empty feed instead (C3).

  • PBP-110040rejected

    Add a card before moving to a paid plan.

    The plan is unchanged. A paid plan is charged when it starts, so it needs a card on file first; add one under Billing.

  • PBP-110041rejected

    The payment processor did not accept that card.

    The card on file is unchanged. The payment processor would not accept the token as a payment method; a token is what the processor’s own card form returns, and never a card number, which this API refuses to receive.

  • PBP-110042rejected

    An invoice is past due. Update the card to settle it before changing plan.

    The plan is unchanged. An invoice is being retried; updating the card retries it at once, and the plan can change once it is paid. Playback is unaffected throughout: past due is a grace period, not a gate (§5.5, §L9).

  • PBP-110043rejected

    This account is on a contract. Contact us to change its plan.

    Nothing changes. Business and Enterprise are sold on a contract rather than self-serve (§7.1 publishes the first three tiers), so their plan is changed by the vendor, not from the dashboard.

  • PBP-110044rejected

    No such invoice.

    Nothing is returned. The invoice does not exist; an invoice id from another account reads the same way.

  • PBP-110045rejected

    The card was declined, so the plan was not changed.

    The plan is unchanged and nothing is owed: an upgrade is charged before it takes effect, and a declined charge undoes it. The message says why the processor declined. A renewal that is declined is not refused like this — it is retried (L9, dunning), and playback continues throughout.

  • PBP-110046rejected

    That event is not signed by the payment processor.

    Nothing changes. The payment processor’s event could not be verified as its own — unsigned, tampered or malformed — so it is not acted on. The processor retries a real one; billing never depends on an event arriving.

  • PBP-110060rejected

    No such API token.

    Nothing changes. The token does not exist, or belongs to another account, which reads the same way.

  • PBP-110061rejected

    No such webhook endpoint.

    Nothing changes. The endpoint does not exist, or belongs to another account, which reads the same way.

  • PBP-110062rejected

    That URL cannot receive webhooks.

    The endpoint is not saved. A webhook URL must be https, carry no credentials, and name a host that resolves only to public addresses — never loopback, a private network, link-local or a cloud metadata address. The same rule is applied again at every delivery, because DNS can change after registration.

  • PBP-110063rejected

    No such webhook delivery.

    Nothing is sent again. The delivery does not exist, or belongs to another account, which reads the same way.

  • PBP-110064rejected

    This account already has as many webhook endpoints as it may.

    The endpoint is not added. An account has at most ten, because every event is sent once to each of them; removing one makes room.

  • PBP-110070rejected

    Encryption is included from the Growth edition.

    Nothing changes. Encryption is included from Growth (§7.2). An item encrypted before a downgrade stays encrypted, and can always be switched off.

  • PBP-110071rejected

    Only media uploaded here can be encrypted.

    Nothing changes. Encrypting re-encodes the uploaded original, so media registered by URL cannot be encrypted here.

  • PBP-110080rejected

    DRM pass-through is included from the Business edition.

    The media item is not saved. DRM pass-through is included from the Business edition (§7.2). Protection already stored stays, and keeps playing after a downgrade; only adding or changing it is refused.

  • PBP-110081rejected

    DRM packaging is not configured on this deployment.

    Nothing is stored. The deployment has no DRM_SEALING_KEY, so a content key could not be stored sealed, and it is never stored any other way; setting it switches DRM packaging on.

  • PBP-110082rejected

    Only media uploaded here can be packaged with DRM.

    Nothing changes. DRM packaging re-encodes the uploaded original, so media registered by URL cannot be packaged here.

  • PBP-110083rejected

    Set the property’s DRM licence servers first.

    Nothing changes. Packaging needs the property's DRM settings — at least one licence server, and a key unless the item brings its own — set first under Media → DRM.

  • PBP-110084rejected

    Media is still packaged with this property's DRM settings.

    Nothing is removed. A packaged item's licence descriptors, and its key unless it has its own, come from these settings; switch DRM off on every item first.

  • PBP-110085rejected

    This item is encrypted. Switch encryption off before packaging it with DRM.

    Nothing changes. An item is either encrypted with AES-128 (Tier 2) or packaged with DRM, never both; switch the one it has off first (playback-object, DRM packaging).

  • PBP-110090rejected

    Single sign-on is included from the Business edition.

    Nothing is shown or changed. Included from the Business edition (§7.2); below it a registered provider is inert and requires nothing of anyone.

  • PBP-110091rejected

    That domain is verified by another account.

    Nothing changes. A domain is verified by one account at most; the account holding it removes it first.

  • PBP-110092rejected

    No such domain.

    Nothing changes. Another account’s domain reads the same way.

  • PBP-110093rejected

    The TXT record was not found yet. DNS changes can take a while to spread — try again later.

    The domain stays unverified: its DNS did not answer with the TXT record shown. DNS changes can take hours to spread.

  • PBP-110094rejected

    Register an identity provider first.

    Nothing changes until an identity provider is registered.

  • PBP-110095rejected

    Verify a domain before requiring single sign-on for it.

    SSO is not required. It applies to verified domains, and there are none yet.

  • PBP-110096rejected

    Turn on your second factor before requiring single sign-on: it is how owners get in when the identity provider cannot.

    SSO is not required. Owners with a second factor are the way in when the identity provider is down, so the owner requiring it needs one first.

  • PBP-110097rejected

    The identity provider’s metadata was refused.

    Nothing is registered. The metadata could not be read, or is another identity provider’s: remove the old one and register again.

  • PBP-110100rejected

    Signing-certificate digests belong to Android keys.

    Nothing is saved. A signing-certificate digest names the key an Android app is signed with; Apple’s platforms give an SDK nothing it could compare one with (licence-protocol, The signing certificate).

  • PBP-110110rejected

    Warehouse export is included from the Business edition.

    Nothing is set. Warehouse export is included from the Business edition (telemetry-schema, Scheduled export); a destination already set below it is kept and not written to.

  • PBP-110111rejected

    Warehouse export is not configured on this deployment.

    Nothing is set. The deployment has no EXPORT_SEALING_KEY, so a destination's credentials could not be stored sealed; setting it switches warehouse export on.

  • PBP-110112rejected

    Another property already exports to that bucket and prefix.

    Nothing is set. Another property already exports to that endpoint, bucket and prefix, and an export's object key carries no property, so sharing one would overwrite that property's hours; use a distinct prefix per property.

  • PBP-110120rejected

    The uploaded file is not the size that was declared for it.

    The upload is discarded and nothing is stored or counted. What arrived was not the size the upload declared when it was opened, and storage is allowed and counted by that declaration. Uploading the file again from the start stores it.

  • PBP-110121rejected

    This video is taller than this deployment can encode.

    The item is not encoded and stays without a hosted source. Its original is taller than this deployment decodes (MEDIA_MAX_INPUT_HEIGHT, 2160 unless an operator set it), and decoding it would run the encoder out of memory. Scaling it to 4K or below and uploading it again encodes it. Nothing already playing is touched.

  • PBP-110122rejected

    This video is not available in your country.

    The hosted file is not served to this viewer: the item carries a georestriction rule, the rule was signed into the link, and the country the edge reports for the request is outside it. The answer is HTTP 451 with this code as its body. Only hosted media is refused — the page, the player and every licence check carry on — and a request whose country the edge cannot tell is served, because an unknown is not a refusal (C3). Changing the rule takes effect on links signed after the change.

  • PBP-110123rejected

    This video is taller than your plan accepts.

    The item is not encoded and stays without a hosted source. Its original is taller than the account's plan accepts (plans.encode.maxInputHeight, P3 lever 7) though this deployment could decode it; the reason the item records names the plan's limit. Scaling it to that height and uploading it again, or moving to a plan that accepts it, encodes it. A plan change re-encodes nothing already made.

  • PBP-110131rejected

    That key belongs to another property.

    Nothing is saved. An app may name a key of its own property only, as it may a player or a playlist.

  • PBP-110132rejected

    An app's key must be a web key.

    Nothing is saved. An app names one web key, the one its pages embed; an Android, iOS or Roku key names its app from the key instead, when it is issued.

  • PBP-110133rejected

    That app belongs to another property.

    Nothing is saved. A key may name an app of its own property only; pick one from the property the key is issued in.

  • PBP-110134rejected

    Generated captions are not included in your plan.

    No captions are generated and nothing already on the item changes. The account's plan includes no transcription (plans.encode.transcribeMinutes absent or zero). Uploading a caption file still works on every plan.

  • PBP-110135rejected

    This month's transcription minutes are used up.

    No captions are generated and nothing already on the item changes. Generating these would take the account past the minutes of transcription its plan includes this calendar month (plans.encode.transcribeMinutes), counted in minutes of source like an encode minute. Uploaded captions are unaffected, and the allowance starts again on the first of the month or on a plan that includes more.

  • PBP-110136rejected

    Captions cannot be generated for this video here.

    No captions are generated and nothing already on the item changes. Either this deployment does not transcribe (MEDIA_TRANSCRIBE is off), or the item has no uploaded original to take the audio from — media registered by URL is never fetched for transcription. Uploading a caption file works either way.

  • PBP-110170rejected

    Origins belong to web keys, not Android or iOS keys.

    Nothing is stored. Origins belong to a web key: a page’s origin is what the manifest service checks it against. An Android or iOS key is limited by its apps instead — its bundle identifiers and, on Android, its signing certificates.

  • PBP-110171rejected

    Enter a valid email address to subscribe.

    Nothing is stored and no mail is sent. Subscribing to status notices needs one email address of at most 320 characters. An address that is valid gets the same answer whether it is new, waiting for confirmation or already subscribed, so the route cannot be used to find out who is subscribed.

  • PBP-110172rejected

    Too many subscription requests for this address. Try again in an hour.

    Nothing is stored and no mail is sent. One address may be subscribed at most five times an hour, beyond the public surface’s own per-address limit, so the form cannot be used to flood someone’s inbox with confirmation mail. The confirmation already sent still works.

  • PBP-110180rejected

    No such live stream.

    The request is refused as not found. A live stream belonging to another property and one that does not exist get the same answer, for the reason PBP-109008 gives.

  • PBP-110181rejected

    This stream is on air. Stop the encoder before deleting it.

    Nothing is deleted. A stream on air cannot be removed out from under its viewers; stop the encoder first. Its recording, once it ends, is an ordinary media item and is deleted as one.

  • PBP-110182rejected

    This stream key is not valid.

    The encoder’s connection is closed before anything of it is encoded or stored. An unknown key, a rotated one, a deleted stream and a suspended account all get the same answer, so a key cannot be guessed at. No viewer is affected: nothing was published.

  • PBP-110183rejected

    This stream is already on air from another encoder.

    The second encoder’s connection is closed before anything of it is encoded; the stream already on air carries on untouched. One stream key carries one encoder at a time. Stop the first, or rotate the key, which ends neither session but refuses the old key from the next connection on.

  • PBP-110190rejected

    Nothing embeddable at that URL.

    Answered 404, with nothing about why: the URL is not a share URL on this deployment, names nothing, names an item that is unpublished, scheduled, expired or still encoding, a playlist with nothing playable, or a suspended account. One answer for all of them, so the endpoint cannot be used to learn that a hidden id exists.

  • PBP-110191rejected

    Only the JSON format is offered.

    Answered 501, as oEmbed 1.0 requires for a format the provider does not offer. Only json is offered; ask again without format or with format=json.