canonical: https://jentic.com/apis/centurylink.com/centurylink # Centurylink Fulfillment Request The CenturyLink Fulfillment Request API retrieves a fulfillment request and its associated line items by request identifier. It surfaces order fulfillment data that originates in Salesforce through an intermediary service layer, so downstream systems can read fulfillment details without a direct Salesforce connection. The API exposes a single read operation focused on fulfillment request lookup. ## For AI agents Retrieve a fulfillment request and its associated line items by request identifier through the CenturyLink Fulfillment Request API. ## Scope Does not handle order creation, payment capture, or shipping labels. Use for retrieving Salesforce-originated fulfillment request data only. ## Capabilities - Retrieve a fulfillment request and its data by request identifier - Read the line items associated with a fulfillment request - Look up order fulfillment details that originate in Salesforce ## Use cases ### AI Agent Fulfillment Lookup An AI agent connected through Jentic can answer order-status questions by retrieving a fulfillment request and returning its line items. The CenturyLink service layer reads fulfillment data sourced from Salesforce, so the agent reports details without opening a separate Salesforce session. Example prompt: Retrieve the fulfillment request for a given request identifier and return its line items ### Order Fulfillment Status Checks Keep support and operations teams informed by pulling fulfillment request details on demand. The API returns the request and its associated line items so a workflow can surface current fulfillment information for a customer order. Example prompt: Fetch the line items for a fulfillment request identifier and report their details ### Fulfillment Data Sync Feed a downstream datastore or dashboard by reading fulfillment requests on a schedule. Because the data originates in Salesforce and is exposed here through a service layer, an integration can mirror fulfillment details without a direct Salesforce link. Example prompt: Retrieve a fulfillment request by identifier and write its line items to a downstream store ## Key resources - **Fulfillment Request** — Retrieve fulfillment request data and its associated line items by identifier ## 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:** 65 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 79 / 100 - AI-Readiness & Agent Experience: 56 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/centurylink.com/centurylink/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 ``` ## Why Jentic - **Setup:** Wiring this CenturyLink API by hand means setting up its X-Application-Key, X-Digest, and X-Digest-Time header auth and the signed request flow yourself. Through Jentic you install once, import it from the API Directory, store the keys once, and your agent calls it. - **Permission scoping:** This API exposes a single read operation, so a rule simply allows your agent to retrieve fulfillment requests and grants nothing more. There are no write or delete actions in the surface to worry about. - **Credential handling:** Your CenturyLink API keys 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 'look up a fulfillment request', and Jentic returns the CenturyLink operation with its input schema so the agent calls it with the right request identifier. ## Related APIs - **ShipStation API** — ShipStation manages order fulfillment and shipping for e-commerce stores. - **AfterShip API** — AfterShip tracks shipments across carriers after fulfillment. ## FAQ ### What authentication does the CenturyLink Fulfillment Request API use? The API authenticates with API key headers, per its OpenAPI spec: an `X-Application-Key` identifies the application, and an `X-Digest` with an `X-Digest-Time` carry a time-stamped request signature. Through Jentic these keys are stored encrypted by your own Jentic One instance and injected at call time, so they never appear in the agent's prompt or logs. ### Can I look up order fulfillment with the CenturyLink API? Yes. The API retrieves a fulfillment request and its associated line items by request identifier. Because the underlying data originates in Salesforce, this read operation lets a workflow surface fulfillment details without a direct Salesforce connection. ### Is there a CenturyLink MCP server? You do not need an MCP server to give your agent this CenturyLink API. Jentic connects it directly from the API Directory: import it, store your keys once, and your agent retrieves fulfillment requests through the operation the API already exposes. The operation is discovered on demand, so no extra tool definitions are loaded into the agent's context. ### Can I limit what my agent is allowed to do with the CenturyLink API? Yes. The API exposes a single read operation, so a rule can allow your agent to retrieve fulfillment requests and nothing else. There are no write or delete actions to grant, and every call the agent makes is logged. ### How do I retrieve a fulfillment request through Jentic with the CenturyLink API? Search Jentic for 'look up a fulfillment request', which returns the CenturyLink operation with its input schema, then supply the request identifier and the agent runs it. To run it on your own infrastructure, install Jentic One from its GitHub repo.