canonical: https://jentic.com/apis/jaggaer.com/jaggaer

# Jaggaer Advanced Sourcing Optimizer (ASO) API

The Jaggaer Advanced Sourcing Optimizer (ASO) API drives strategic sourcing and procurement optimization across three services. The customer host service manages customers, users, sourcing events, and templates; the event service works with event attributes, bids, awards, and suppliers; and the Quay service submits and tracks optimization jobs. Agents create events from templates, collect bids, run optimization, and retrieve the awarded scenario.

## For AI agents

Create sourcing events from templates, manage event attributes and bids, submit optimization jobs, and retrieve awarded scenarios.

## Scope

Does not handle purchase orders, invoicing, or payment execution. Use for sourcing event management and award optimization only.

## Capabilities

- Create sourcing events from templates for a given customer and user
- List and read sourcing events along with their attributes and bids
- Create and update event attributes individually or in batches
- Submit optimization jobs and track their status to completion
- Retrieve bids and the awarded scenario for a sourcing event

## Use cases

### AI Agent Sourcing Event Creation

An AI agent connected through Jentic stands up a sourcing event from an approved template for a named customer and user, then lists that user's events to confirm it was created. Templates keep the event structure consistent, so the agent can launch repeatable sourcing rounds without rebuilding attributes each time.

Example prompt: Create a sourcing event from a template for a given customer and user, then list the user's events

### Optimization Job Orchestration

After bids are collected, an agent submits an optimization job to the Quay service and polls its status until the run finishes, then reads the result. This automates the compute-heavy award step that would otherwise require a user to watch the job in the portal.

Example prompt: Submit an optimization job for an event and poll its status until the run completes

### Bid and Award Retrieval

To report sourcing outcomes, an agent retrieves the bids submitted for an event and the awards for the preferred scenario. The async award and bid operations return structured results an agent can summarize for a buyer.

Example prompt: Retrieve the bids for an event and the awards for the preferred scenario

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/oauth2/token` | Generate an OAuth 2.0 access token |
| POST | `/chost/{customerHostId}/user/{userId}/template/{templateId}/apiEvent` | Create a sourcing event from a template |
| GET | `/chost/{customerHostId}/user/{userId}/apiEvents` | List events by user |
| GET | `/event/{eventId}/apiAttributes` | List event attributes |
| POST | `/submitJob` | Submit an optimization job |
| GET | `/jobStatus/{jobId}` | Get optimization job status |
| GET | `/event/{eventId}/apiBids/async` | Get bids for an event |

## Key resources

- **Customer Host Service** — Manage customers, users, sourcing events, and templates
- **Event Service** — Work with event attributes, bids, awards, and suppliers
- **Quay Service** — Submit, cancel, and track optimization jobs
- **Authorization** — Generate OAuth 2.0 client-credentials access tokens

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 68 / 100
  - AI Discoverability: 80 / 100
- **View full report:** https://jentic.com/apis/jaggaer.com/jaggaer/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Jaggaer ASO API by hand means obtaining OAuth 2.0 client-credentials tokens, attaching the API key header, and routing calls across its three service hosts yourself. Through Jentic you install once, import Jaggaer from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Jaggaer puts the customer host id and event id in the URL path (`/chost/{customerHostId}/...`, `/event/{eventId}/...`), so a rule can pin your agent to operations on one customer host or event. You choose the operations it may call, so destructive ones like deleting an attribute are not included unless you add them.
- **Credential handling:** Your Jaggaer OAuth client credentials and API key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a sourcing event' or 'submit an optimization job', and Jentic returns the matching Jaggaer operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Salesforce** — Salesforce manages the supplier and stakeholder relationships behind a sourcing event.
- **Airtable** — Airtable stores and shares the sourcing data an agent prepares or exports.
- **SAP Concur** — SAP Concur handles the downstream spend and expense of awarded suppliers.

## FAQ

### What authentication does the Jaggaer ASO API use?

It uses OAuth 2.0 client-credentials access tokens together with an API key in the `X-API-Key` header, as declared in its OpenAPI spec. You request a token from the token endpoint, then send it with the API key when calling the services. Through Jentic both are stored encrypted by your own Jentic One instance and injected at call time.

### Can I submit an optimization job with the Jaggaer ASO API?

Yes. The job-submit operation queues an optimization run for an event, and you can poll the job-status operation and then retrieve the awards for the resulting scenario once it completes.

### What are the rate limits for the Jaggaer ASO API?

The OpenAPI spec does not specify rate limits for the Jaggaer ASO API. See the Jaggaer ASO documentation at https://asodocs.jaggaer.com for the current limits that apply to your account.

### Can I limit what my agent is allowed to do with the Jaggaer ASO API?

Yes. Write a rule that allows only the event-read and bid-read operations, so the agent can review events and bids but cannot create events, change attributes, or submit optimization jobs, and every call it makes is logged.

### How do I create a sourcing event with the Jaggaer ASO API through Jentic?

Search Jentic for 'create a sourcing event', add the Jaggaer ASO API from the directory, and store your OAuth client credentials and API key once. Your agent requests a token, then creates the event from a template. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Jaggaer ASO API MCP server?

You don't need an MCP server to give your agent the Jaggaer ASO API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the event, bid, and optimization-job operations. That keeps extra tool definitions out of the agent's context.