Zaprite connector for Okou
Connect Zaprite to read payment orders, contacts, event tickets, and webhook configuration, or manage authorized checkout workflows.
Sales & operations · API Key
Use Zaprite in Okou
Zaprite API for reading payment orders, contacts, event tickets, and webhook configuration, and for explicitly authorized checkout, ticket, contact, order, and webhook operations.
Once connected, supported Zaprite actions can become steps in a reusable workflow alongside the other services your team uses. Run the workflow once, on a schedule, or when an event starts it.
What you can do with Zaprite
- Read Zaprite contacts. Responses can include saved payment profiles that Zaprite documents as usable with the order charge endpoint, so this permission is explicit-only.
- Read Zaprite orders. Responses can include checkout, receipt, invoice, ticket, and saved payment-profile capabilities, so this permission is explicit-only.
- Read Zaprite event tickets. Responses include ticket URLs that anyone with the URL can view or use, so this permission is explicit-only.
- Read Zaprite webhook IDs, destination URLs, labels, and creation timestamps for the connected organization.
- Create a Zaprite contact record.
- Create a payment-ready Zaprite order and optionally invoice data. This changes provider state and may trigger later payment notifications.
- Issue Zaprite event tickets. This can email attendees, update ticket inventory, and incur the documented Standard Ticket Fees.
- Create a Zaprite webhook subscription that sends events to an external destination.
How the Zaprite connector works
A connected service becomes one permissioned step in the work you hand off.
- 1
Connect Zaprite
Choose API Key.
- 2
Choose the work
Use only the supported actions your workflow needs.
- 3
Run it your way
Start it once, schedule it, or attach an event trigger.
Connect Zaprite securely
Use the connection method that fits your account and grant only the access the workflow needs.
- API Key
Connector access is controlled per service and per action, so a workflow does not need broader access than the work you ask it to do.
What Zaprite covers
The topics this connector's published operations touch.
- bitcoin payments
- payment orders
- invoicing
- event tickets
- webhooks
Zaprite connector questions
- What can Okou do with Zaprite?
- Connect Zaprite to read payment orders, contacts, event tickets, and webhook configuration, or manage authorized checkout workflows. Documented actions include: Read Zaprite contacts. Responses can include saved payment profiles that Zaprite documents as usable with the order charge endpoint, so this permission is explicit-only. Read Zaprite orders. Responses can include checkout, receipt, invoice, ticket, and saved payment-profile capabilities, so this permission is explicit-only.
- How do I connect Zaprite to Okou?
- Connect Zaprite using API Key. The connection controls which supported actions a workflow can use.
- Can Zaprite run in an automated workflow?
- Yes. After it is connected, supported Zaprite actions can run in reusable Okou workflows on demand, on a schedule, or from an event trigger.
More sales & operations connectors
Explore other connectors in the same product category.
ZeeRM
Connect ZeeRM to read an existing lead by ID through its Dashboard API.
Zabun
Connect Zabun to read Belgian real-estate properties, contacts, offices, media, requests, tasks, and related CRM data.
Zeliq
Connect Zeliq to check credit balances and start asynchronous work-email or mobile-phone enrichment jobs.
