canonical: https://jentic.com/apis/swaggerhub.copa-airlines/api---revenue-management-bidprice---v10

# Copa Airlines API - Revenue Management BidPrice - v1.0

Gets BidPrice's information by Flight. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically gets the list of bidprices by flight and cabin. Covers 1 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Gets the list of Bidprices by flight and cabin
- Manage developer tools data programmatically
- Integrate API - Revenue Management BidPrice - v1.0 into automated workflows
- Query and filter API - Revenue Management BidPrice - v1.0 records by parameters
- Monitor API - Revenue Management BidPrice - v1.0 operational status and events

## Use cases

### Developer Tools Operations

Use the API - Revenue Management BidPrice - v1.0 to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including gets the list of bidprices by flight and cabin.

Example prompt: Call GET /{flightnum}/{departdate}/{opcarrier}/{origin}/{destination} to gets the list of bidprices by flight and cabin

### Data Retrieval and Monitoring

Query API - Revenue Management BidPrice - v1.0 resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary API - Revenue Management BidPrice - v1.0 endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call API - Revenue Management BidPrice - v1.0 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'gets the list of bidprices by flight and cabin', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{flightnum}/{departdate}/{opcarrier}/{origin}/{destination}` | Gets the list of Bidprices by flight and cabin |

## Key resources

- **default** — Operations related to default

## Why Jentic

- **Setup:** Wiring the Revenue Management BidPrice API by hand means registering its subscription key, deciding whether to send it in the Ocp-Apim-Subscription-Key header or the subscription-key query, and building the flight, date, and route path yourself. Through Jentic you install once, import the BidPrice API from the API Directory, store the subscription key once, and your agent calls it.
- **Permission scoping:** This API exposes a single read operation that takes flight, date, carrier, origin, and destination in the URL path, so scope your agent to that bid-price lookup. You choose which operations are allowed, so the agent can only run the lookups you grant.
- **Credential handling:** Your Copa subscription key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get bid prices for a flight and cabin', and Jentic returns the matching Revenue Management BidPrice operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the API - Revenue Management BidPrice - v1.0 use?

The API - Revenue Management BidPrice - v1.0 uses an API key passed in the `Ocp-Apim-Subscription-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I gets the list of bidprices by flight and cabin with the API - Revenue Management BidPrice - v1.0?

Yes. Use the GET /{flightnum}/{departdate}/{opcarrier}/{origin}/{destination} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API - Revenue Management BidPrice - v1.0?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I gets the list of bidprices by flight and cabin through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'gets the list of bidprices by flight and cabin'. Jentic returns the matching API - Revenue Management BidPrice - v1.0 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API - Revenue Management BidPrice - v1.0 have?

The API - Revenue Management BidPrice - v1.0 exposes 1 endpoints covering default operations.

### Can I limit what my agent is allowed to do with the API - Revenue Management BidPrice - v1.0?

Yes. Because you run Jentic One yourself, you decide which operations and credentials your agent may use, and this API exposes only a single read operation, the GET bid-price lookup that takes flight number, departure date, operating carrier, origin, and destination in the URL path. Grant your agent just that lookup and it cannot call anything else, since it can only run the operations you allow. Your Copa subscription key is stored encrypted in your own instance and injected at execution time, so it never enters the agent's prompt or context.