Skip to content

Zapier Integration Details

Authentication

The SecPaid Zapier integration authenticates via OAuth2 Authorization Code flow:

  1. The user is redirected to SecPaid's /authorize endpoint to grant Zapier access.
  2. Upon approval, SecPaid redirects back to Zapier's redirect URI with an authorization code.
  3. Zapier exchanges the code for an access token via a POST to SecPaid's /token endpoint.
  4. The access token is included in the Authorization header of all subsequent API calls.

Zapier handles token storage and refresh automatically.

Available Actions

create_LinktoPay

Creates a new payment link.

  • Input fields: recipient_note (optional), amount (required)
  • Request: POST https://app.secpaid.com/api/v1/createLink
  • Returns: Payment link details including pay_link and QR code URL

getpayin

Retrieves a list of received payments.

  • Input fields: search (optional), page (optional), limit (optional)
  • Request: POST https://app.secpaid.com/api/v1/getPayInTransactions
  • Returns: Array of pay-in transactions

Rate Limiting

Rate limits are applied per OAuth connection. Exceeding the limit returns 429 Too Many Requests. Zapier's built-in retry mechanism handles transient rate limit errors automatically.

Error Handling

Standard HTTP status codes are used. Zapier surfaces errors in the Zap history with the response message, making it easy to debug failed steps. Use Zapier's monitoring dashboard to inspect individual Zap runs.

API Version Note

The Zapier integration uses the V1 API with OAuth2. This is intentional — V1 is the interface designed for low-code automation platforms. For direct server-side integrations, use the V2 API with an API key instead.