PayPal REST
Your agent works in PayPal REST with your key, and never holds it.
- 7 days free
- Cancel anytime
- Nothing to install
- Kind of work
- Payments and billing
- How you connect
- Client ID and secret
- What waits for you
- Nothing, until you turn on asking
What your agent can do there
Look up payments and customers, issue refunds, manage subscriptions and invoices.
- payments
- orders
- payouts
- refunds
- invoices
PayPal REST also runs a remote MCP server of its own. Connect it the same way, and your agent gets its tools too. See the remote MCP servers
At the provider
Technical details
- Hosts
- api-m.paypal.com, api-m.sandbox.paypal.com
- Key type
- oauth2-cc
- Key goes in
- Authorization
Which calls read, write or destroy
| When | Class |
|---|---|
| GET ^/v1/notifications/webhooks(-event-types|-events(/[^/]+)?|-lookup(/[^/]+)?|/[^/]+(/event-types)?)?$ | read |
Without a matching rule, GET, HEAD and OPTIONS read, POST, PUT and PATCH write, and DELETE and any other method destroy. A recipe rule only raises a GET the vendor changes something with to a write. No recipe rule makes a call destructive.
Token IP filtering
If the provider can limit a token to IP addresses, allow Sallyport's outbound address. The connection form shows it, ready to copy.
Bring a service the catalogue has never seen
Add its web address and your key, and your agent uses it like any of the 827. If your agent runs into a service you haven’t added, it sends you a link.
- 7 days free
- Cancel anytime
- Nothing to install