canonical: https://jentic.com/apis/paypal.com/invoices

# Paypal Invoices

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.

## For AI agents

Programmatically create draft invoice, list invoices. Covers 22 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Create draft invoice
- List invoices
- Send invoice
- Cancel sent invoice
- Record payment for invoice
- Delete external payment

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create draft invoice', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **invoices** — Use the `/invoices` resource to create, update, and send invoices and invoice reminders. To manage i
- **search-invoices** — Use the `/search-invoices` resource to search for and list invoices that match search criteria.
- **templates** — Use the `/templates` resource to create, list, show details for, update, and delete invoice template
- **merchant-config** — Use the `/merchant-config` resource to create, update and show details of merchant configuration.
- **estimates** — Use the /estimate resource to create, update, and send estimates.

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API

## FAQ

### 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.