canonical: https://jentic.com/apis/limberfy.com/limberfy # Limberfy Swagger LINKA - OpenAPI 3.0.3 The LINKA API from Limberfy connects a buyer's ERP to the LINKA supplier portal: it publishes purchase orders with their line items and PDF, updates or removes them by order number, and queries orders and supplier invoices by date range, currency, and evaluation status. It also registers supplier companies by their Peruvian RUC tax id and manages the supplier users who operate on each company's records. LINKA follows SUNAT rules for electronic payment vouchers in Peru. ## For AI agents Publish, update, and look up purchase orders, query supplier invoices by series and status, and register supplier companies and their users on the LINKA portal. ## Scope Does not issue electronic invoices to SUNAT, pay suppliers, or track inventory. Use for publishing purchase orders, checking supplier invoice status, and onboarding suppliers on LINKA only. ## Capabilities - Publish a purchase order with its supplier, client, totals, PDF, and NEC line details from an ERP - Update or remove a purchase order by its order number - Query purchase orders by number, currency, status, order type, or issue and reception date ranges - Look up supplier invoices by series number with filters for evaluation status, currency, and dates - Register a supplier company by RUC and update or remove its details - Add, update, or deactivate supplier users under a company and reset their passwords ## Use cases ### Agent-driven purchase order sync through Jentic An AI agent watching an ERP can push each approved purchase order to LINKA so suppliers see it in their portal, then confirm it landed by querying orders by number. Through Jentic the agent finds the publish and query operations by intent and loads their schemas, so the nested ordenCompra and detallesOrden payload is built from the schema instead of hand-written. Example prompt: Search Jentic for 'publish a purchase order', send order OC-0001 with tipoOrden 'Suministro', moneda 'USD', and its detallesOrden lines, then query purchase orders with number=OC-0001 to confirm it was created. ### Supplier invoice status checks Accounts payable teams in Peru need to know whether each supplier invoice was accepted, observed, or rejected. The LINKA bill query filters by series number (sn), correlative number, evaluation status, currency, and issue or reception date range, so an agent can report on pending invoices without opening the portal. Example prompt: Query bills with sn=F001 and eval_status=0 for issue dates from 01-06-2025 to 30-06-2025 and list the pending invoices. ### Supplier onboarding Before a supplier can work in LINKA, its company is registered by RUC with name, phone, and address, and each person who operates on its records gets a user with a DNI and role. The API covers registering, listing, updating, and removing both companies and users, and changing a user's password. Example prompt: Register a supplier company with its name, ruc, phone, address, first_name, and last_name, then register a user for that ruc with username, password, dni, and role 4. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/token/` | Obtain an authentication token | | POST | `/api/purchase_order/` | Create a purchase order | | GET | `/api/purchase_order/` | Query purchase orders | | PUT | `/purchase_order/{numeroOrden}/` | Update a purchase order | | GET | `/api/bill/` | Query supplier invoices | | POST | `/v1/api/register_company/` | Register a supplier company | | POST | `/v1/api/register_provider/` | Register a supplier user | ## Key resources - **Purchase orders** — Orders published from the buyer's ERP, with supplier, client, totals, PDF, and NEC line details - **Bills** — Supplier invoices queried by series, correlative number, evaluation status, currency, and dates - **Supplier companies** — Companies registered and managed by RUC - **Supplier users** — Users under a supplier company, addressed by RUC and DNI ## 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:** 48 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 72 / 100 - Developer Experience & Jentic Compatibility: 73 / 100 - AI-Readiness & Agent Experience: 22 / 100 - Agent Usability: 94 / 100 - Security: 75 / 100 - AI Discoverability: 68 / 100 - **View full report:** https://jentic.com/apis/limberfy.com/limberfy/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 LINKA by hand means exchanging your RUC, username, and password for a JWT and building the nested ordenCompra and detallesOrden payload correctly. Through Jentic you install once, import LINKA from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** LINKA puts the order number and the supplier RUC in the URL path (`/purchase_order/{numeroOrden}`/ and `/v1/api/get_providers/{RUC}`/), so a rule can pin your agent to one purchase order or one supplier company. You choose the operations it may call, so destructive ones like deleting a supplier company or a purchase order are not included unless you add them. - **Credential handling:** Your LINKA credentials 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 'publish a purchase order' or 'check invoice status', and Jentic returns the matching LINKA operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **BILL AP Vendor Transactions** — Accounts payable bills and vendor payments - **Jaggaer Sourcing Optimizer** — Sourcing events, bids, and award optimization - **Alegra API** — Latin American accounting with invoices and payments - **Mindee OCR API** — Field extraction from invoice and receipt images ## FAQ ### What authentication does the LINKA API use? The LINKA API uses HTTP bearer authentication with a JWT per its OpenAPI spec. You obtain the token from the token operation by posting your ruc, username, and password, then send it in the Authorization header. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at request time. ### Is there a Limberfy LINKA MCP server? You don't need an MCP server to give your agent the LINKA API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the purchase order, bill, and supplier operations on demand without loading another server's tool definitions into its context. ### Can I filter purchase orders by status with the LINKA API? Yes. The purchase order query takes a status filter with values such as 0 for pending, 2 for completed, and 4 for partial, plus filters for order number, currency, total, order type (oc_type), and issue or reception date ranges. ### What are the rate limits for the LINKA API? The OpenAPI spec does not specify rate limits. Check with Limberfy at https://limberfy.com for current limits on your LINKA account. ### Can I limit what my agent is allowed to do with the LINKA API? Yes. For example, write a rule that allows only the purchase order query and the bill query, so the agent can report on orders and invoice status but cannot publish, change, or remove orders or touch supplier companies and users. Every call it makes is logged. ### How do I check supplier invoice status with the LINKA API through Jentic? Search Jentic for 'query supplier invoices', load the bill query operation, and pass the required series number sn with optional eval_status, currency, and date filters in DD-MM-YYYY format. Jentic injects your bearer token at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.