> 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/understand-integration-states-and-capability-levels.md).

# Understand integration states and capability levels

Understand what each integration state means before you connect a platform, demand source, or delivery surface.

Podigee Audio Video Ad Server uses separate states for configuration, testing, certification, and live use. The states tell you what Podigee has checked and what still depends on the external provider.

Do not treat a saved connector as a live connector. Do not treat a local contract check as provider certification. A connection can be ready for one capability and blocked for another capability.

## The state path

The normal path is:

**Configured > Tested > Locally conformant > Provider certified > Active**

The path can stop at **Blocked** or **Unsupported**. An active connection can later become **Suspended** when an operator or a safety rule stops its use.

| State                | What it means                                                                    | What you can do                                                   |
| -------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Configured           | The connection record and its contract details are saved.                        | Review the values and start a test.                               |
| Tested               | A test run has been requested or completed.                                      | Read the result and correct failed inputs.                        |
| Locally conformant   | Podigee's contract, security, media, and response checks passed.                 | Continue to provider or validator certification.                  |
| Validator conformant | A required format or validator check also passed.                                | Continue to the provider's certification step when required.      |
| Sandbox certified    | The provider accepted the tested capability in its sandbox.                      | Prepare an activation request for the permitted environment.      |
| Production certified | Current provider evidence confirms the capability for production use.            | Activate the exact capability and monitor it.                     |
| Active               | The exact version is bound to an allowed serving or booking operation.           | Use the connection in a Flight, deal, destination, or report.     |
| Suspended            | The connection is intentionally not used for new operations.                     | Inspect the reason, repair it, and resume only after checks pass. |
| Blocked              | A policy, security, contract, certification, or authority check prevents use.    | Read the blocker and correct the source.                          |
| Unsupported          | Podigee does not support the requested capability or cannot verify its contract. | Choose another supported capability or keep the source inactive.  |

The state belongs to an exact connection version and capability. A new endpoint, credential, protocol, media kind, or provider contract can require a new test and new evidence.

## Capability levels are more precise than a connector state

One connector can expose several capabilities. For example, a demand partner can support VAST for audio, OpenRTB for video, and no CATS operation. Each capability has its own protocol, operation, media authority, tracker authority, limits, and certification evidence.

Use the capability level when you decide whether a Flight or destination can use the connection:

* **Registered** means the capability is recorded in the connection contract.
* **Tested** means the declared request and response path was exercised.
* **Conformant** means the response, media, security, and evidence checks passed.
* **Certified** means the required provider or validator evidence is current.
* **Activated** means the exact capability is allowed in the selected environment.

The highest state for one capability does not upgrade another capability. A provider certified for VAST is not automatically certified for OpenRTB or CATS.

## Read the state in the application

Open **Monetization > Integrations** to review connections and their delivery or platform boundaries. Open **Monetization > Marketplace** to review demand partners that can book eligible Inventory. Open **Monetization > Campaigns > Add flight** to see only the provider capabilities that are currently available for the selected Flight.

![The current One Podigee Integrations page shows the integration overview, the certification action, and the notice that preparation does not change listener delivery.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-29049f991698a6013b33e27944dc1eb6b21e2653%2Fdoc-monetization-103-integrations-overview.png?alt=media)

*Read the delivery safety notice before you prepare a show or certify a connection.*

![The One Podigee Add flight form shows the delivery destination and the choice between Podigee delivery and a connected demand provider.](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)

*A connected provider appears as a choice only after its required checks pass.*

When you choose **Connected demand provider**, the form filters the provider, protocol, and operation lists from the active authority. It does not accept a provider ID or operation as free text. A missing option is a useful signal that the capability is not active for this use.

For a platform-controlled destination, read the authority boundary before you interpret the state. For example, a Spotify connection can be configured and ready in Podigee while Spotify still controls final playback, insertion, and destination reporting.

![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.*

## What each check proves

### Configuration check

This check proves that the connector has an owner, purpose, endpoint or platform identity, data flow, and declared capabilities. It does not prove that the endpoint accepts requests.

### Security and transport check

This check proves that the endpoint and credential reference meet the allowed transport and access rules. Podigee stores credentials separately from the connector details. A passing transport check does not prove a valid ad response.

### Media and policy check

This check proves that the declared audio or video media authority, tracking authority, markets, privacy use, and fallback are compatible with the connection. It prevents a technically valid response from bypassing publisher or listener protections.

### Contract and validator check

This check proves that the request and response match the declared standard or platform contract. It can include VAST, OpenRTB, CATS, Apple HLS, Spotify distribution, or another supported contract. The result is evidence for the exact version, not a permanent guarantee for every later version.

### Provider check

This check proves that an external provider accepted the required capability or returned current production evidence. A local or validator result cannot replace this check when the provider owns the certification boundary.

### Activation check

This check binds the exact verified version to the selected environment and operation. It records the authority, effective time, capability, and evidence used for the activation. Changing the connector after activation creates a new version or requires a new check.

## Local checks and external certification are different

Use this rule when you read a status:

* **Local contract conformance** means Podigee verified the declared contract with local fixtures.
* **Validator conformance** means a required validator also accepted the output.
* **Sandbox certified** means the external provider accepted the capability in a sandbox.
* **Production certified** means current provider evidence supports production use.

Local checks do not contact an external provider and do not prove production delivery. A provider can still reject a capability after local conformance. The UI must keep the boundary visible so an operator does not activate a connection on the wrong evidence.

## When a connection becomes blocked

Podigee can block a connection when:

* the endpoint is not allowed or the credential is missing;
* the selected provider version is not the current exact version;
* certification evidence is expired or does not cover the requested capability;
* the response or media does not pass the declared contract;
* the provider does not support the selected protocol or operation;
* privacy, market, rights, or publisher rules prevent the requested use;
* the provider contract is unknown, changed, or not available for verification.

Blocked means no new serving or booking operation should use that capability. Existing records and last confirmed evidence remain available for investigation.

## When to suspend instead of delete

Suspend a connection when you need to stop new use but keep its history, external identifiers, certification evidence, and previous results. Use suspension for a provider incident, credential rotation, a planned maintenance period, or a temporary policy decision.

Do not delete a connection to hide a failed test or a previous delivery result. Create a new version when the endpoint, provider contract, or capability changes. Keep the old version for audit and for explaining earlier decisions.

## If a Flight cannot use the connection

1. Open **Monetization > Integrations** and read the connection state.
2. Confirm the required capability, protocol, media kind, and destination.
3. Check the certification expiry and the environment.
4. Review **Monetization > Operations** for the blocker or failed test.
5. Repair or certify the connection before you create a new Flight binding.
6. Use **Podigee delivery** when the Campaign must run while the external capability is blocked.

Do not copy a provider or protocol value from an older Flight. Select a current capability from the form after the connection is active again.

## Expected result

You can tell the difference between saved configuration, a passing local check, external certification, and live use. Each Flight or destination uses only the exact capability whose security, media, policy, and provider evidence is current.


---

# 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/understand-integration-states-and-capability-levels.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.