Official vendor OpenAPI document · agent-readyPaymentsPayment Processingoauth222 EndpointsREST
For Agents
Programmatically create draft invoice, list invoices. Covers 22 operations with oauth2 authentication.
Use for: I need to draft invoice, I want to invoices, Search for send invoice, Find all send invoice reminder
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Use the Invoicing API to create, send, and manage invoices. You can also use the API or webhooks to track invoice payments. When you send an invoice to a customer, the invoice moves from draft to payable state. PayPal then emails the customer a link to the invoice on the PayPal website. Customers with a PayPal account can log in and pay the invoice with PayPal. Alternatively, customers can pay as . The API exposes 22 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the Invoices to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Invoices, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaypal.com%2Finvoices" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaypal.com%2Finvoices" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Invoices API.
Create draft invoice
List invoices
Send invoice
Cancel sent invoice
Record payment for invoice
Delete external payment
Use Cases
Patterns agents use Invoices API for, with concrete tasks.
★ Payments Operations
Use the Invoices to perform payments operations programmatically. The API provides 22 endpoints covering core functionality including create draft invoice, list invoices, send invoice.
Call POST /v2/invoicing/invoices to create draft invoice
Automated invoices Management
Automate invoices operations by combining multiple Invoices endpoints. Agents can list invoices and then send invoice in a single workflow.
Call GET /v2/invoicing/invoices to list invoices, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Invoices 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 oauth2 tokens manually.
Search Jentic for 'create draft invoice', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
22 endpoints — use the invoicing api to create, send, and manage invoices.
METHOD
PATH
DESCRIPTION
POST
/v2/invoicing/invoices
Create draft invoice
GET
/v2/invoicing/invoices
List invoices
POST
/v2/invoicing/invoices/{invoice_id}/send
Send invoice
POST
/v2/invoicing/invoices/{invoice_id}/remind
Send invoice reminder
POST
/v2/invoicing/invoices/{invoice_id}/cancel
Cancel sent invoice
POST
/v2/invoicing/invoices/{invoice_id}/payments
Record payment for invoice
DELETE
/v2/invoicing/invoices/{invoice_id}/payments/{transaction_id}
Delete external payment
POST
/v2/invoicing/invoices/{invoice_id}/refunds
Record refund for invoice
POST
/v2/invoicing/invoices
Create draft invoice
GET
/v2/invoicing/invoices
List invoices
POST
/v2/invoicing/invoices/{invoice_id}/send
Send invoice
POST
/v2/invoicing/invoices/{invoice_id}/remind
Send invoice reminder
POST
/v2/invoicing/invoices/{invoice_id}/cancel
Cancel sent invoice
POST
/v2/invoicing/invoices/{invoice_id}/payments
Record payment for invoice
DELETE
/v2/invoicing/invoices/{invoice_id}/payments/{transaction_id}
Delete external payment
POST
/v2/invoicing/invoices/{invoice_id}/refunds
Record refund for invoice
Jentic AI Readiness Score
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.
I
Invoices
- Foundational (D+)48/100
60
Foundational Compliance50
Developer Experience & Jentic Compatibility24
AI-Readiness & Agent Experience94
Agent Usability85
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
60
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B-Signals: 4
66%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
50
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
0%
Example Validity
Percentage of examples that conform to their schemas.
100%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
24
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
39%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
58%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
85
Security
Trust, risk posture, and security compliance.
Grade: ASignals: 1
85%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring PayPal Invoices by hand means running its OAuth 2.0 flow, refreshing Bearer tokens, and choosing the right sandbox or live host before you can draft, send, or refund invoices. Through Jentic you install once, import Invoices from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
Invoices puts the invoice id in the URL path (/v2/invoicing/invoices/{invoice_id}/send), so a rule can pin your agent to one invoice: it can send and remind on that invoice and nothing else. You choose the operations it may call, so cancelling an invoice or deleting a recorded payment is not included unless you add them.
Credential isolation
Your PayPal OAuth client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time, with token refresh handled for you. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a draft invoice' or 'send an invoice reminder', and Jentic returns the matching Invoices operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Invoices API through Jentic.
What authentication does the Invoices use?
The Invoices uses OAuth 2.0 for authorization. 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 create draft invoice with the Invoices?
Yes. Use the POST /v2/invoicing/invoices endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Invoices?
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 create draft invoice through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create draft invoice'. Jentic returns the matching Invoices operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Invoices have?
The Invoices exposes 22 endpoints covering invoices, search-invoices, templates operations.
Can I limit what my agent is allowed to do with the PayPal Invoices API?
Yes. Jentic One is self-hosted by you, so your own rules decide which invoicing operations and credentials the agent may use. Because the invoice id sits in the URL path, such as /v2/invoicing/invoices/{invoice_id}/send, you can pin the agent to a single invoice and allow only sending and reminding on it. Cancelling an invoice, recording a payment, or deleting an external payment stay off limits unless you explicitly grant those operations.
GET STARTED