> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/concepts-and-reference/capability-and-service-status.md).

# Capability and service status

Check the current delivery capabilities, provider grants, service state, known problems, and certification boundary before you activate a destination.

Capabilities and services can change independently. A connector can be healthy while one protocol is blocked. A provider can be enabled while its production grant is missing. The application shows the current state and the evidence that supports it.

This article explains the status words and the places where the current authority appears. It does not copy a temporary status into a static list.

## Status words

| Status               | Meaning                                                                                    | Operator action                                               |
| -------------------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------- |
| Available            | The capability is supported and its current checks allow use.                              | Use it within the displayed scope.                            |
| Limited              | The capability works only for a declared media, surface, market, provider, or environment. | Read the limitation before planning.                          |
| Configured           | The connection details are saved, but use is not yet allowed.                              | Start the required checks.                                    |
| Tested               | The declared request or response path was exercised.                                       | Read the evidence and continue certification.                 |
| Locally conformant   | Podigee checks passed for the exact profile.                                               | Continue to platform or provider certification when required. |
| Sandbox certified    | The external provider accepted the capability in a sandbox.                                | Use only in the permitted environment.                        |
| Production certified | Current provider evidence allows production use.                                           | Activate the exact capability and monitor it.                 |
| Blocked              | Policy, security, authority, contract, or certification prevents use.                      | Read the blocker and repair the source.                       |
| Experimental         | The capability is available only under an explicit experiment grant.                       | Do not use it for an ordinary Campaign.                       |
| Unsupported          | The current product does not support or cannot verify the capability.                      | Choose another supported path.                                |
| Suspended            | An operator or safety rule stopped new use while history remains.                          | Inspect the reason and resume only after checks pass.         |

The status belongs to an exact capability version. A new endpoint, credential, media profile, provider contract, or destination can create a new status even when the connector name is unchanged.

## Current first-party delivery status

The current first-party surfaces are:

| Surface                     | Current capability                                                 | Boundary                                                           |
| --------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------ |
| RSS audio                   | Available for compatible audio representations and approved breaks | Podigee controls the serving path and qualified delivery evidence. |
| Podigee HLS audio and video | Available for compatible HLS presentations and interstitials       | Podigee controls the host-side presentation and decision path.     |
| Apple Podcasts video        | Limited by Apple HLS and platform association evidence             | Podigee hosts the HLS path; Apple controls destination playback.   |
| Spotify                     | Limited by the enabled Spotify capability and provider grant       | Spotify controls destination execution and final reporting.        |
| Owned player                | Available after the player contract passes its checks              | The player must accept media, events, and fallback.                |
| External demand             | Available only for a certified provider and protocol               | Provider response, privacy, timeout, and fallback checks apply.    |
| YouTube ad execution        | Unsupported in the current product                                 | Keep the capability inactive.                                      |

This table describes the product boundary. The current per-workspace state, provider grant, and certification evidence appear in the application and can change without a documentation release.

![The One Podigee Add flight form shows the media, Inventory, delivery, goal, and measurement fields.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5fc4e4d261a5d8c83f52f4569ec7dfeb55c32a06%2Fdoc-monetization-034-add-flight.jpg?alt=media)

*The delivery choices show only capabilities that are available for the selected Flight.*

## Where to read the current authority

Use the most specific authority first:

1. **Campaigns > Add flight** shows capabilities that are selectable for the current media, Inventory, surface, and workspace.
2. **Integrations** shows connector versions, capability states, certification expiry, and provider receipts.
3. **Operations** shows current incidents, failed checks, provider results, and repair actions.
4. **Evidence & Money** shows delivery, analytics, report, and commercial evidence.
5. **Monetization settings** shows policy, privacy, cost, and fallback boundaries.
6. The service status link in the application help shows a platform-wide incident or maintenance state when one exists.

Do not use an old screenshot, an old provider receipt, or a copied status table as current authority. Read the status timestamp, capability version, environment, and evidence expiry together.

## Provider and platform grants

Provider capability is a separate state from connection health.

| Check                 | What it proves                                       | What it does not prove                           |
| --------------------- | ---------------------------------------------------- | ------------------------------------------------ |
| Credential valid      | The connection can authenticate                      | The provider accepts the selected operation.     |
| Endpoint healthy      | The endpoint answers a health request                | The response is valid or billable.               |
| Local conformance     | The request and response match the selected contract | Production provider certification.               |
| Sandbox certification | The provider accepted the test capability            | Production quota, market, or revenue enablement. |
| Production grant      | The provider permits the exact operation             | Successful delivery for every request.           |
| Destination receipt   | The platform accepted the submitted operation        | Listener or viewer playback.                     |

Spotify can be ready in Podigee while Spotify is still processing a show, episode, order, or sponsorship. Apple host-side HLS can pass its checks while Apple association or device playback still needs current platform evidence.

![The current One Podigee Spotify setup shows a fixed impression goal with an ad position, Spotify CPM, and impression limit for the selected Flight.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-35081efb7aa287a9072d7a53f24df0bcf66e2f0d%2Fdoc-monetization-059-spotify-standard.png?alt=media)

*A destination-specific setup can have its own capability and execution state.*

## Read a blocked or limited capability

Open the exact capability and check:

1. Status and status time.
2. Capability version and environment.
3. Media kind and destination.
4. Provider or platform grant.
5. Certification result and expiry.
6. Policy, privacy, rights, and fallback boundary.
7. Current incident or repair operation.
8. Last valid version and safe alternative.

The status should give one primary blocker and a recovery link. If the blocker is an unknown provider contract, keep the capability blocked. Do not select a similar protocol as a substitute.

## Incident and maintenance behavior

When a platform or provider incident affects only one capability, keep unrelated surfaces active. The application should show:

* the affected capability and media kind;
* the start time and last update;
* the current fallback or safe behavior;
* the affected workspaces or destinations;
* the next check or recovery condition;
* the evidence and owner for the incident.

A status incident must not silently change a Campaign, Creative, Inventory, or finance record. A pause, fallback, or replacement is a versioned operation with its own receipt.

## When to activate a capability

Activate only when all required conditions are true:

1. The connector is owned and scoped to the correct workspace.
2. The endpoint, credential, and transport pass security checks.
3. The media profile and destination match.
4. The privacy, rights, policy, and fallback rules are current.
5. The provider or platform grant covers the exact operation.
6. The required validator or sandbox evidence is current.
7. The configured review or solo confirmation is complete.
8. One representative test produces a decision, delivery, analytics, and money result.

Do not activate because a connector is configured or because a health check is green.

## Expected result

You can see what is available now, what is limited, what is blocked, and why. You can distinguish a local check from provider certification and a destination receipt from playback. A capability is activated only for the exact version, surface, media, environment, and authority that current evidence supports.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/concepts-and-reference/capability-and-service-status.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.