ONVO API
See the ONVO documentation for integration details and examples.
Authentication
- HTTP: Bearer Auth
- HTTP: Bearer Auth
Publishable API keys are intended for client-side source code, where they are exposed in browser-accessible code.
You can identify them by the onvo_test_publishable_key_ or onvo_live_publishable_key_ prefix.
Publishable API keys are used to create new payment methods and authenticate the ONVO SDK in your integration.
The Authorization header must start with 'Bearer ' followed by the Publishable API key from your ONVO dashboard.
Example:
'Authorization': 'Bearer onvo_test_publishable_key_VL3ln7fwTC1DiJGvGE0H5A-XYPNJDmoGtwcduXYTRtsuKRc4d1PXEh33Ju9RZRXGJkX0KsRV5-F540ciRCQosQ'
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | Bearer onvo_api_key |
Secret API keys are intended for server-side source code, where they must be kept properly protected.
Your Secret API keys have many privileges, so keep them secure. Do not share your Secret API keys or use them in client-side code.
You can identify them by the onvo_test_secret_key_ or onvo_live_secret_key_ prefix.
Secret API keys are used to create new payment intents and subscriptions.
The Authorization header must start with 'Bearer ' followed by the Secret API key from your ONVO dashboard.
Example:
'Authorization': 'Bearer onvo_test_secret_key_VL3ln7fwTC1DiJGvGE0H5A-XYPNJDmoGtwcduXYTRtsuKRc4d1PXEh33Ju9RZRXGJkX0KsRV5-F540ciRCQosQ'
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | Bearer onvo_api_key |