Browse guides
Connect the Collect API and signed events
Create scoped Ops Pro credentials and handle event delivery without bypassing review.
In this guide
Create a scoped credential
An Owner with active Ops Pro opens Developers, chooses the required scopes and creates a credential with an expiry of at most 90 days. Copy the token once and store it securely. Removing its creator, expiry, revocation or loss of Ops Pro access prevents API use. It cannot substitute for a staff or customer session.
Read records and prepare intake
The Developers reference documents paginated customer, obligation, invoice, receipt, request and resolution reads. Write scopes can create customers, import balances and prepare draft invoices or requests using stable retry keys. Writes also require the creator to remain an Owner or Reviewer. Issuing, sending, approval and customer acceptance stay in the merchant/customer workflow.
Verify and deduplicate events
Configure a public HTTPS endpoint and selected events, then copy its signing secret once. Verify the exact request body against x-resolvely-signature. Events can repeat or arrive out of order: deduplicate event IDs and compare versions for each resource. Delivery history shows bounded retries; an Owner can replay failed delivery without repeating the financial action. Disabling the endpoint stops queued delivery.
Still need help? Contact support with the case ID and a description of the issue.